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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuine value by enumerating the returned fields (patient, practitioner, location, wanted services, preferred days/time, tags, active flag) — important since there is no output schema. It says nothing, however, about result volume, default filtering (e.g. are archived/closed entries returned by default), or ordering, which matters for a 13-param list tool.

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 compact fragments, front-loading the returned fields before the endpoint. No filler; each clause carries information. The 'GET /waitlists' tail is mildly redundant with the tool name but confirms the HTTP method.

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 field enumeration compensates usefully for return-value documentation, and all 13 parameters are covered by the schema. Still missing: default result behavior (does it return closed/archived entries?), pagination expectations, and any note that this is a clinic-wide list rather than a per-patient lookup, which leaves gaps for a high-parameter list tool.

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 every one of the 13 parameters (pagination cursors, isActive, patientId, date ranges, include_archived, etc.) is already documented in the schema. The description mentions only the fields of a waitlist entry and the 'active flag', adding no filter semantics beyond the schema. Baseline 3 applies.

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?

The description names the resource (waitlist entries) and the endpoint (GET /waitlists), and lists the fields each entry carries, so an agent can infer this is a read of waitlist records. However, it never states the action or scope in words ('list all waitlist entries'), relying on the field enumeration and the URL to convey purpose. It is adequate but vague as a purpose statement.

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 guidance on when to use this versus alternatives (e.g. checking whether a patient is already waiting, or following up on closed entries), nor any prerequisites or exclusions. The agent must infer usage entirely from the tool name and the isActive parameter description.

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