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

readOnlyHint=true already declares the safety profile, and the description largely repeats this with “Read only.” It does add value by disclosing the underlying endpoint (GET /sale/services) and the shape of returned attributes, which helps set expectations. However, it omits pagination behavior despite 12 params including limit/offset, and adds no auth or rate-limit context.

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 tightly packed sentences with no filler: the resource and returned fields come first, then the read-only note and endpoint. Every clause carries information.

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?

For a 12-parameter read-only listing tool with full schema coverage and no output schema, the description covers the resource, the returned fields, and the safety profile. It would be complete if it addressed pagination (since limit/offset exist) or clarified its relation to list_sales, but the schema compensates for the former.

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 all 12 parameters (including the non-obvious location_id tax computation and per-staff pricing) are already fully documented in the schema. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 a specific verb and resource (“list the pricing options”) and resolves Mindbody's ambiguous “services” terminology by equating it with class packs, drop-ins, and intro offers. It also names the returned attributes (price, online price, count, expiry). It is clear, but stops short of explicitly contrasting itself with the nearby sibling list_sales, which an agent might otherwise confuse with it.

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?

The description says what the tool lists but gives no guidance on when to choose it over list_sales, list_bookable_items, or the other catalog siblings. There is no mention of prerequisites, typical scenarios, or exclusions; the agent must infer usage from the resource name alone.

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