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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond them by disclosing the result surface — up to 100 items carrying unit, quantity, minimum and a low-stock flag — which tells the agent this is a bounded, non-paginated list rather than a writable or streaming endpoint.

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?

Three short sentences, front-loaded with the triggering intent before the return shape and the exclusion. No filler, no restatement of the title, and each sentence carries distinct information.

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?

An output schema exists, so the description need not define return values, and all four optional parameters are fully documented in the schema. Combined with annotations covering safety, an agent has what it needs; only the sibling routing for the excluded case is left implicit.

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%, with limit, search, clinicId and lowStockOnly each documented including defaults, bounds and the list_clinics provenance for clinicId. The description only indirectly gestures at lowStockOnly via "what is running low" and adds no syntax or format meaning beyond the schema, so the 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 resource (clinic stock items) and the exact question it answers — "how much of a supply is left" or "what is running low". The closing exclusion "Not for procedure prices" separates it from list_procedures, so an agent can pick between them without opening either schema.

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?

Gives an explicit natural-language trigger plus one exclusion, which is more than most definitions offer. It stops short of naming the sibling to use for the excluded case (list_procedures) and never mentions set_inventory_quantity as the write counterpart, so the routing is implied rather than spelled out.

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