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

readOnlyHint=true already tells the agent this is a safe read. The description adds the GET /procedures endpoint, which is marginally useful, but says nothing about pagination behavior, default page size, or result ordering despite four parameters that drive listing.

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 short clauses, front-loaded with the action and resource; nothing is padded. It is arguably too terse to be maximally useful, but every word earns its place.

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 four-parameter listing tool with no output schema, the essentials are covered by annotations and the rich schema, but the description omits listing-specific behavior an agent may need — pagination defaults and whether results are bounded or filtered server-side.

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 four parameters are already documented in the schema (including pagination and the subdomain default). The description only restates the patient scoping already covered by patient_id, adding no new syntax or format meaning. 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?

States a specific verb (List) and resource (clinical procedures) plus the scoping option and the underlying endpoint. It is clearly distinguishable from siblings, which operate on different resources (appointments, patients, providers), though it does not name any sibling.

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?

"Optionally scoped to a patient" implies the main usage branch — pass patient_id when you want one patient's procedures — but there is no explicit when-to-use/when-not guidance or reference to an alternative search tool.

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