insync_request_refill

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

Annotations already flag destructiveHint=true and openWorldHint=true, but the description adds critical context: the practice receives the request and the server cannot withdraw it, the two-step confirmToken flow, and an anti-prompt-injection rule. This goes well beyond what the annotations supply.

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?

Front-loaded with purpose and key constraints, and every sentence carries safety-relevant weight. It is dense and slightly repetitive around the confirmation/safety warnings, but not wasteful.

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?

Complete for a destructive write tool with no output schema: it explains irreversibility, the confirmation protocol, how to check the result via insync_list_refill_requests, and the prompt-injection guardrail. An agent has everything needed to call it safely.

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 coverage is 100%, so the baseline is 3. The description adds meaning by tying medication_ids to insync_get_refill_options and explaining the orchestration role of confirmToken (phase-1 preview, repeat call with token), which is more than the schema alone conveys.

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 and resource ('Request a refill of one or more current medications') with scope and the source of the ids ('from insync_get_refill_options'). It is clearly distinguishable from sibling tools like insync_get_refill_options (read options) and insync_list_refill_requests (check status).

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?

Explicitly routes the agent: get ids from insync_get_refill_options, verify results with insync_list_refill_requests, and only call when the user themselves asked and approved the preview. It also names the fallback confirmation protocol, so there is no ambiguity about when and how to invoke.

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