get_sales_velocity

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

Clearly indicates a read operation with no side effects. No annotations, but the description is sufficient for a simple read tool with no parameters.

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?

Single sentence with no wasted words, perfectly 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?

Lists the data fields, but no output schema or return structure details. Adequate for a simple read tool with zero parameters, though 'days of cover' and 'sell-through pace' could be defined.

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?

No parameters defined, so description adds no parameter info. Schema coverage is 100% (empty), warranting a baseline score of 4.

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?

Description clearly states the tool reads sales velocity by ASIN and specifies the exact metrics (rolling units sold, days of cover, sell-through pace) and time windows (7/30/90 day), making it distinct from sibling tools.

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?

No explicit when-to-use or alternatives, but the specific metrics imply use cases. Lacks comparison to siblings like get_inventory_health or get_product_details.

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