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

Annotations already declare readOnlyHint=true, so 'Read only' in the description largely repeats structured data. It does add the upstream endpoint (GET /sale/services) and enumerates returned fields, which is modest extra context, but no auth requirements or pagination behavior are disclosed.

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 tight sentences plus an endpoint tag, all front-loaded with the resource and purpose first. Nothing is padded, though the return-field list could be trimmed against the schema.

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?

With 12 params and no output schema, the description partially compensates by naming returned fields (price, online price, count, expiry), but it omits pagination guidance despite limit/offset params and offers no routing between similarly named listing tools.

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% across all 12 parameters, so the schema already documents each filter's meaning (including caveats like location_id computing TaxRate rather than filtering). The description adds no parameter-level meaning beyond the schema, making the baseline 3 correct.

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?

States a specific verb (List) and resource (pricing options/services) and clarifies the domain terminology with the parenthetical 'class packs, drop-ins, intro offers', plus the return fields. It does not explicitly differentiate from close siblings like list_bookable_items or list_sales, so it stops short of a 5.

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 when-to-use, when-not-to-use, or alternative routing is provided. 'For sale at the site' scopes the resource but gives no guidance on choosing this versus list_bookable_items or list_sales.

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