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

readOnlyHint=true already declares the safety profile, and "Read only" restates it rather than adding information. Genuinely new context is limited to the "completed sales" filter and the returned field groups; pagination behavior, result caps, and site/auth scoping (the description says "at the site" but no site parameter exists) are undisclosed.

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?

One tight sentence with the resource and scope front-loaded, followed by a short read-only and endpoint note. Nothing is padded, though the "Mindbody: GET /sale/sales" trailer is developer trivia rather than agent-facing value.

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 no output schema, the description usefully enumerates what comes back (purchased items, payments, client), which compensates for the missing return definition. The main gap is the unexplained "at the site" framing with no site parameter and no pagination note despite limit/offset.

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%, so limit, offset, sale_id, payment_method_id and the two date bounds are all self-documented. The description only paraphrases the date/time-range filter and adds no format, default, or interaction detail beyond the schema; baseline 3 is 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?

Specific verb and resource ("List completed sales") with explicit scope (site + date/time range) and a preview of the payload (purchased items, payments, client). It reads clearly against siblings like mindbody_list_client_visits or mindbody_list_services, though it never names those alternatives.

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?

Usage is implied by the date/time-range scope but never stated as guidance: there is no when-to-use, when-not-to-use, or pointer to a sibling tool such as visit or membership listings. The agent must infer the appropriate context from the scope alone.

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