insync_list_refill_requests

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered for free. The description adds the record content (status and dates per request), which is useful, but it says nothing about ordering, pagination, or how much history is returned.

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 sentences, no filler, with the resource and scope front-loaded and the negative disambiguation placed where it matters. Every clause 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 no-required-param, read-only list tool with no output schema, the description covers what is returned (status and dates per request) and what it is not. Only ordering and volume of history remain unstated, which is a minor gap given the strong annotation coverage.

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?

There is a single optional parameter with 100% schema description coverage and an enum, so the schema fully documents 'view' including the default. The description adds nothing about its effect on the result rows, 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?

Specific verb ('List') plus specific resource ('patient's prescription refill-request history') and even the shape of the records ('the rows of the refill grid'). It explicitly excludes the adjacent write action ('Does NOT submit a refill request'), which cleanly separates it from the sibling insync_request_refill.

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 establishes the read-only viewing context and implicitly routes submission to insync_request_refill by negation, so an agent knows which of the two refill tools to pick. It stops short of naming that sibling explicitly or stating prerequisites such as a patient identifier.

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