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

No annotations are provided, so description carries burden. It mentions data returned (id, type, title, status) but does not disclose pagination behavior beyond limit param, sorting, or whether it returns both codes and automatic discounts in one call. It implies read-only but doesn't state side effects (likely none). Adequate but not rich.

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: first lists what it returns and purpose, second provides routing hint. Zero filler, front-loaded with key info. The routing line is brief but useful.

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?

Tool is simple with 2 params and full schema coverage, no output schema needed. Description covers purpose, return fields, and usage context. Slight gap: doesn't mention if discounts are returned in any order or how statuses are counted, but sufficient for agent selection.

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% and parameters are simple: companyId (required) and limit with default/max. Description adds 'company-scoped' context for companyId and mentions statuses, but does not explain how limit interacts or whether discount type filtering is possible. Baseline 3 is appropriate as schema covers semantics well.

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 it lists discount codes and automatic discounts from Shopify, including id, type, title, and status. It adds scope (code vs automatic) and clarifies use case before creating or referencing promotions. Distinguishes from create_shopify_discount_code and other list_shopify_* 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?

Explicitly says 'Use to see what promotions currently exist before creating or referencing one', which provides clear context. However, it does not explicitly mention when NOT to use or name alternative tools for filtering or more detailed discount info. Sibling names like create_shopify_discount_code imply creation, but no direct comparison is made.

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