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

Annotations already declare readOnlyHint=true, and the description's 'GET /operatories' simply restates that it is a read. It adds no behavioral context such as pagination, ordering, or what happens with an invalid location_id. With annotations carrying the safety profile, the description contributes almost nothing new.

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 plus an endpoint reference, with the resource and its scope front-loaded. Nothing is padded, though the trailing 'GET /operatories' is close to redundant given the annotations.

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, no-required-param read tool with annotations covering safety, this is minimally adequate. However, there is no output schema, so the description could reasonably say what is returned (a list of operatories) or whether results are paginated, and it does not.

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 both subdomain and location_id are already documented in the schema. The description's 'for an institution' and 'scoped to a location' loosely map to those two params but add no format or edge-case detail beyond them; 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 (operatories), and helpfully glosses the domain term as 'chairs/rooms' for an agent that may not know NexHealth vocabulary. It does not differentiate itself from the adjacent list_* siblings (e.g. list_locations), but the resource is unambiguous.

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 location' implies when to pass location_id, which is the only usage decision this tool has. No alternatives are named and no prerequisites (e.g. needing a valid subdomain) are stated, so guidance is implied rather than explicit.

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