format_plan_block

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

No annotations provided. Description states generation but lacks details on side effects or idempotency. However, tool is straightforward, so minimal transparency is acceptable.

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 sentence, no wasted words. Could add minor context, but effective and front-loaded with 'MANDATORY'.

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?

With 5 parameters, low schema coverage, and no output schema or annotations, the description fails to provide sufficient detail for correct invocation, especially for parameter values and output format.

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 only 20% (only preferred_provider has description). Description does not explain tier, reason, estimated_files, or estimated_tokens, leaving their meaning unclear.

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 generates a formatted output block for plan end, distinguishing it from siblings like classify_task and get_model_suggestions.

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 says 'MANDATORY' and 'to be pasted at the end of every plan', indicating when to use. No explicit when-not-to or alternatives, but given mandatory nature, it's sufficient.

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