List Available Commodities

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

Annotations already indicate a safe read (readOnlyHint=true) and open world (openWorldHint=true). The description adds value by clarifying the result is 'fetched live from the API, grouped by category,' providing helpful behavioral context beyond annotations.

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 extremely concise: two sentences covering purpose, usage, and behavior. Every sentence adds value with no wasted words, and the key information 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 the lack of an output schema, the description adequately hints at the return format ('full catalog ... grouped by category'). The tool is simple, and no further details (like pagination) are necessary, making it nearly complete.

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?

With zero parameters and 100% schema description coverage, no parameter details are needed. The description adds 'No parameters needed' for clarity, meeting the baseline expectation for a param-free tool.

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 lists all available commodities for price queries, specifying concrete use cases like when the user asks for commodities, codes, or error handling. It naturally distinguishes from siblings that focus on prices, alerts, or other functionality.

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 explicitly tells when to use the tool (for commodity availability queries, codes, error handling) and notes no parameters needed. It doesn't explicitly state when not to use or list alternatives, but the context is clear enough for an AI agent.

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