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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real operational context beyond them: one Mindbody API call per invocation and hard pagination ceilings (50 per call, offset up to 100). The note that there is no location filter because each sale carries LocationId is genuinely useful scoping behavior. It does not describe the shape of a returned sale record, which is the main remaining gap given there is no output 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 purposeful content is front-loaded, but the block mixes URL, call-count, alternative routing, pagination, and a location caveat without clear separation, and repeats the sales_summary recommendation. The final sentence restating the resource feels tacked on rather than additive.

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 7-parameter, all-optional listing tool with full schema coverage, the description covers routing and pagination limits adequately. It leaves open what a sale record contains and how the tool behaves when no date range is supplied, both of which matter for a record-listing endpoint with no output schema.

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 limit/offset/date/payment filters are already fully documented and the description's restatement of them adds little. The one piece of value beyond the schema is the clarification that siteId functions as a header and does not filter results by location. Baseline 3 is appropriate.

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 concrete verb+resource ("Get Sales — GET /sale/sales") and clarifies the unit returned: individual sale records completed at a site, at most 50 per call. It explicitly disambiguates from sales_summary and studio_kpis, so an agent can route without opening schemas. The trailing sentence "Get sales completed at a site" is a bit redundant with the header but does add scope.

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?

Names alternatives with conditions: sales_summary for revenue totals/breakdowns, studio_kpis for a period scorecard, and this tool for record-level lookup. The guidance is clear but repetitive — sales_summary is recommended twice in near-identical phrasing ("totals and breakdowns" then "a sales breakdown"), which adds noise rather than new routing information.

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