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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds that this is an availability-discovery step preceding booking, which is useful, but says nothing about the volume/shape of results, pagination behavior, or how availability records are structured — relevant for a 10-param search. With annotations carrying safety, this is an adequate-but-thin addition.

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 sentences, zero filler: the capability and its scope come first, then the workflow pointer and the underlying endpoint. Nothing is redundant with the name or title.

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 10-parameter search tool with no output schema, the description effectively summarizes what is returned (staff / location / time windows) and when to call it. Missing is any note on result volume or pagination handling despite limit/offset being exposed, which is a minor gap given the otherwise thorough 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%, and the schema itself documents defaults, formats (ISO 8601 examples), and per-field intent for all 10 parameters. The description adds no parameter-level detail beyond naming session types, so the 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 specific verb and resource ('Find appointment availability') and then enumerates the result dimensions — staff, location, time window. This scope is clearly distinguishable from siblings like mindbody_list_staff_appointments or mindbody_list_services without opening any schema.

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?

Explicitly positions the tool in a workflow: 'Use before mindbody_add_appointment,' naming a concrete alternative/next step. It gives clear context but no when-not guidance (e.g., it never says to prefer mindbody_list_staff_appointments for reviewing already-booked appointments), so it stops short of full routing.

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