prime-tools
Prime for Tool Development
Load tool development patterns from Module 3 to prepare for building agent tools.
Context
You are about to work on building or modifying agent tools that will be used by Pydantic AI agents. Load the comprehensive patterns and best practices we established in Module 3 for writing agent-optimized tool docstrings.
Read
Read the tool docstring patterns: @.agents/reference/adding_tools_guide.md
Process
Understand and internalize:
- Core Philosophy - How agent tool docstrings differ from standard docstrings
- 7 Required Elements - One-line summary, "Use this when", "Do NOT use", Args with guidance, Returns, Performance Notes, Examples
- Agent Perspective - Writing for LLM comprehension and tool selection
- Token Efficiency - Documenting token costs and optimization strategies
- Anti-patterns - Common mistakes that confuse agents
- Template Structure - The exact format to follow
Pay special attention to:
- "Use this when" (affirmative guidance for tool selection)
- "Do NOT use" (negative guidance to prevent tool confusion)
- Performance Notes (token costs, execution time, limits)
- Realistic examples (not "foo", "bar", "test.md")
Report Back
Provide a concise summary with:
Key Principles (5 bullets max)
- [What are the core principles you understood?]
Critical Distinctions
- [What makes agent tool docstrings different from standard docstrings?]
- [Why does "Do NOT use" matter?]
Template Internalized
- [Confirm you understand the structure you'll follow]
Ready to Apply
- [One sentence confirming you're ready to write agent-optimized tool docstrings]
Keep it scannable - I want to verify understanding in 30 seconds.
More from giladresisi/ai-dev-env
execute
Use when implementing a feature plan file, choosing between sequential and team-based parallel execution with mandatory validation gates
8validate
Use when running comprehensive project validation including tests, type checking, linting, API connectivity checks, and server startup verification
8github_bug_fix:implement-fix
Use when implementing a fix for a GitHub issue that already has an RCA document at docs/rca/issue-{id}.md
8plan-feature
Use when creating a comprehensive implementation plan for a new feature including codebase analysis, API research, and parallel execution strategy
7