update_plan

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses replace vs merge behavior and storage location. No annotations exist, so description carries burden. Missing details on permissions, side effects, or error cases, but sufficient for basic understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph that is informative but slightly verbose. Could be more structured, but every sentence adds value and purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema, description covers purpose, behavior, storage, and cross-referencing. Lacks return value or error details, but overall adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. Description adds context like slugification of name and default replace behavior, but does not substantially enhance parameter understanding beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: documenting feature plans, including files, decisions, and status. It specifies both creation and update, and distinguishes from siblings by focusing on plan management.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance on when to use ('Update existing plans when you complete or change direction on a feature'). Does not explicitly mention when not to use or compare with siblings like save_wisdom or backup_plan, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.