list_price_rules

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

With no annotations provided, the description must convey behavioral traits. It only mentions that the tool uses the Admin GraphQL API and replaces an older workflow. There is no disclosure about permissions, idempotency, side effects, rate limits, or pagination behavior (despite pagination parameters in the schema).

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 two sentences, front-loaded with the primary action. It is concise without redundant words, though it could include more detail without being verbose.

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?

The description lacks context about the return value, pagination handling, and how it differs from sibling list tools. Given the tool has 3 parameters and no output schema, the description should provide more guidance on expected behavior and usage patterns.

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 coverage is 100%, meaning all parameters have descriptions in the schema. The description does not add any additional meaning or examples beyond what the schema provides. Per guidelines, baseline is 3.

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 states 'List code discounts using the Admin GraphQL API', but the tool name is 'list_price_rules', creating potential confusion between code discounts and price rules. The sibling tool 'list_code_discounts' exists, further blurring the distinction. While the verb 'list' is clear, the resource is ambiguous.

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 versus alternatives like 'list_code_discounts' or 'list_automatic_discounts'. There is no mention of use cases, prerequisites, or when not to use the tool.

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