task_break_down

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

Without annotations, the description discloses key behaviors: the tasks array can be empty and then must be filled by the model, and complexity_level is not saved. This adds context beyond the basic function.

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?

Two sentences, front-loaded with the core purpose, and every word adds value. No fluff.

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?

The description covers the main usage and a key behavioral pattern, but it does not mention return values or prerequisites (e.g., milestone must exist). Given no output schema, this is a gap for completeness.

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?

The description explains the complexity_level parameter's role (reference only, not saved) and the tasks array's behavior, adding meaning beyond the schema which only has a terse description for complexity_level. Schema coverage is 33%, so the description compensates.

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 verb 'break down' and resource 'milestones into detailed tasks', distinguishing it from sibling tools like project_create_milestone or task_update. It also provides a specific behavioral detail about the tasks array.

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?

The description explains when to use the tool (to break down milestones) and gives a guideline on how to fill the tasks array if empty. However, it does not explicitly exclude alternative scenarios or compare with siblings.

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