commodity_price_query

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

Annotations already include readOnlyHint=true, so the description's 'Query' is consistent. The DEMO note adds caution but no additional behavioral traits like rate limits or stability. Without annotations, description would need more; with annotations, it's adequate.

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 two sentences, front-loaded with the core purpose, and every phrase adds value. No redundant or filler content.

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 the simple query tool with full schema and output schema present, the description covers purpose and data reliability. It could mention output format slightly, but overall complete enough for agent context.

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% with clear enums for commodity and market. The description does not add new meaning beyond what the schema provides (e.g., 'Kenya markets' aligns with market choices). Baseline score of 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 states 'Query current commodity prices at Kenya markets', using a specific verb (Query) and resource (commodity prices). It distinguishes from siblings via the 'Western parallel' note and DEMO notice, clearly identifying its scope.

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 a DEMO warning and verification instructions, but does not explicitly guide when to use this tool over siblings like market_overview or price_trend_analysis. The 'Western parallel' offers context but not direct exclusion criteria.

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