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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower; the description adds the endpoint mapping but no pagination behavior, rate limits, auth requirements, or empty-result handling. It discloses nothing beyond what the annotations and schema already convey.

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?

A single front-loaded sentence that identifies the resource, then the filters, with no filler. The trailing "Mindbody: GET /appointment/staffappointments" is marginally useful for debugging but is not strictly required for tool selection.

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 an 8-parameter, all-optional list tool with no output schema, the description covers purpose and filters but says nothing about result set shape, paging defaults (limit 100 / offset 0), or ordering. There is no output schema to rely on, so the omission of return-side expectations leaves a modest gap.

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 the baseline is 3 and the schema carries the burden. The description restates the staff/client/appointment-id filters but omits location_ids and pagination parameters entirely and adds no format or default detail beyond the schema.

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 and resource ("List booked appointments") plus the scope it covers ("in a date range, by staff member, client or appointment id — the appointment book"), so an agent can immediately separate it from the sibling write tools mindbody_add_appointment and mindbody_update_appointment. The underlying endpoint (GET /appointment/staffappointments) is also named, anchoring the resource unambiguously.

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 names the filter dimensions, which implies when the tool applies, but never states when to prefer it over alternatives such as mindbody_get_class_visits or mindbody_list_client_visits, nor any prerequisite (e.g., required staff/client/location context). Usage is only implied.

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