sell_hold_decision

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

Annotations already declare readOnlyHint: true. The description adds important behavioral context: it's a DEMO model and recommends verifying prices, indicating reliability limitations beyond the annotation.

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?

The description is three sentences, front-loads the purpose, and every sentence adds value (purpose, parallel, caveat). No wasted words.

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 an output schema present, the description adequately explains the tool's purpose and context ('harvest advisor'). It lacks explicit mention of the output type (recommendation) but the demo warning adds necessary caution. Sufficient for a read-only advisory tool.

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?

Input schema has 100% description coverage for all parameters. The description does not add significant detail beyond the schema; it provides general context (e.g., storage cost in KES) but no syntax or format specifics. Baseline 3 is appropriate.

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 'Give a sell/hold recommendation for a commodity based on price trends', specifying the verb and resource. It also differentiates from sibling tools (e.g., commodity_price_query) by framing it as a decision advisor for harvest 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?

The description provides context ('what should I do with my harvest today?') and a caveat ('DEMO model', 'verify prices'), which guides appropriate use. However, it does not explicitly state when to use this tool versus alternatives like price_trend_analysis.

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