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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, and the description usefully adds the payload scope: up to 100 clinics and explicitly no pet, owner, appointment, or clinical data. That is meaningful added context beyond the structured fields, though it says nothing about failure modes or auth.

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?

The opening clause is redundant, restating the same trigger twice ('when the user wants to open ... when the user requests an interactive clinic browser'), which hurts front-loading. The trailing exclusions are tight and earn their place, but the lead sentence should be compressed.

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 an output schema present and rich annotations, the description only needs to add scoping and routing information, which it largely does via the 100-clinic cap and the data-exclusion statement. It is complete enough to invoke correctly, missing only a pointer to which sibling handles the excluded actions.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the 4 baseline for parameterless tools 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 pairs a specific verb ('open') with a specific resource ('Veterical clinic-selection sidebar') and frames it as an interactive clinic browser, which distinguishes it from data-returning siblings like list_clinics. It stops short of naming an actual sibling to contrast against, so it is clear but not fully differentiated within the toolset.

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?

It gives explicit when-to-use ('when the user requests an interactive clinic browser') plus explicit exclusions ('Not for booking appointments, editing records or medical decisions'). No alternative tool is named for the excluded cases, which keeps it from a 5.

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