keepa_price_history

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

With no annotations, the description must disclose behavior. 'Get historical price data' implies a read-only operation, but it doesn't state whether it is safe, if it consumes API tokens, how many data points are returned, or any rate limit implications. This is a significant gap for a tool that likely interacts with an external API.

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 a single, clear sentence of eight words. It is front-loaded with the action and object, contains no filler, and every word earns its place.

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 tool's complexity (4 parameters, no output schema, no annotations), the description is far too minimal. It fails to mention output format, parameter relationships, or how it fits among siblings. A complete description should at least note that it returns time-series data or that it uses the Keepa API token.

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?

The input schema has 100% description coverage, so the baseline is 3. The tool description adds no additional meaning beyond the schema, such as how parameters interact (e.g., dataType values) or what the response contains. It neither improves nor degrades the schema's clarity.

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 retrieves historical price data for an Amazon product, using the specific verb 'Get' and a specific resource. It distinguishes from siblings like keepa_product_lookup (current data) and keepa_sales_velocity (sales trends), though it does not explicitly name these distinctions.

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 no guidance on when to use this tool versus siblings, no context on use cases, and no exclusions. It simply states what the tool does, leaving the agent to infer its proper role among the ten sibling tools.

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