Get Prices

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

Describes return fields and filtering/pagination behavior, implying a read-only operation. However, with no annotations, it could be more explicit about non-destructive nature.

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, first lists what prices are returned, second covers filtering and pagination. No extraneous text, front-loaded with key information.

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?

Covers purpose, return data, filtering, and pagination. Missing details like default sorting or error conditions, but sufficient for a getter tool with 5 params and no output schema.

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?

Adds context beyond schema by listing returned price fields and explaining price index concept. Schema already covers all parameter descriptions, so baseline 3 plus value from response context.

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?

Clearly states it gets current prices for products and lists specific price fields (selling price, old price, marketing price, etc.), distinguishing it from sibling tools like update_prices or get_product.

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?

Implies usage for price retrieval but does not explicitly say when to use this tool vs alternatives like update_prices or get_product. No exclusions or alternatives named.

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