get_sales_ranks

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

The description discloses that it is a read operation and importantly notes that this is a local introspection stub, which is critical behavioral context. However, it does not explain any side effects, rate limits, or what happens on failure, and annotations are absent.

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 with two focused sentences. The first sentence states the purpose, the second adds the crucial stub limitation. No wasted words.

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?

Despite having 7 optional parameters and no output schema, the description does not explain the return value, supported categories, or how parameters like filters work. The tool is left under-specified for an agent to use effectively.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning beyond the schema; it does not explain parameter interactions or usage patterns.

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 that the tool retrieves 'best seller rank by category' and identifies it as a read operation in the catalog domain. This is specific enough to distinguish from many sibling tools, though it does not elaborate on the exact format or scope of the rank data.

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 guidance is provided on when to use this tool compared to alternatives like get_sales_and_traffic or get_sales_summary. The description lacks any context for tool selection.

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