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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds the underlying API call count ('Mindbody calls: 1'), which is useful cost information, but says nothing about result volume, pagination defaults, or how filtering interacts with the returned set.

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?

It is short and front-loaded, but the first line merely repeats the title and name plus a raw HTTP path, and the disjointed 'Mindbody calls: 1' fragment reads as internal telemetry rather than guidance. Minimal waste in length, but low information density.

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 simple read-only list endpoint with a fully documented six-parameter schema and complete annotations, the description covers the essentials, and no output schema means return values need not be explained. The main gap is the conceptual overlap with get_services and get_session_types, which leaves an agent without disambiguation.

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 six parameters (limit, offset, siteId, onlineOnly, programIds, scheduleType) are fully documented in the schema, which sets the baseline at 3. The description mentions no filters at all and therefore contributes nothing beyond the structured 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?

It gives an endpoint (GET /site/programs) and a purpose sentence, but that sentence says 'service categories offered at a site,' which conflicts with the tool name and blurs the line with siblings get_services and get_session_types. An agent cannot confidently tell whether 'programs' here means service categories or something else.

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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives such as get_services, get_session_types, or find_classes, despite several siblings covering nearby concepts. The reader must infer usage entirely from the name and endpoint.

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