listPriceRules

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

No annotations provided; description only mentions deprecation (future removal). Does not disclose auth requirements, rate limits, or side effects. Minimal behavioral context beyond the deprecation note.

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, front-loaded with action and scope. Efficient but could be slightly more structured without adding length.

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 2 params and no output schema, description is inadequate. Lacks pagination details, parameter semantics, and return structure. Deprecation note is useful but insufficient for complete understanding.

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?

Input schema has 'limit' and 'cursor' with no descriptions. Description does not add any parameter information, resulting in 0% coverage. Agent gets no help on how to use these parameters.

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 lists discounts, covering specific types (code, automatic, BxGy, free-shipping). Also notes deprecation context. However, sibling 'listDiscounts' exists without differentiation, slightly reducing clarity.

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 on when to use this vs. alternatives like 'listDiscounts' or other siblings. Only mentions deprecation but does not provide explicit usage context or exclusions.

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