insync_list_medications

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description usefully enumerates the returned fields, which matters because there is no output schema, but it says nothing about pagination, result caps, or upstream latency for an open-world portal call.

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, front-loaded with the verb and resource, and the field list is compact. The trailing "Choose current, discontinued or cancelled" is slightly terse to the point of ambiguity (choose what — the status filter?), but no content is wasted.

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 only two optional parameters, high schema coverage, and read-only annotations, the definition covers the basics and compensates for the absent output schema by naming the returned fields. It nonetheless omits pagination behavior and whether discontinued/cancelled listings return a materially different record shape.

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 parameters are already fully documented, including the view enum's compact/full/raw semantics. The description's status enumeration merely restates the schema enum and adds nothing for the view parameter, 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?

The description states a specific verb and resource ("List prescriptions / medications on file") and enumerates the concrete fields returned, which makes the tool's scope clear. It does not distinguish itself from nearby siblings such as insync_list_refill_requests or insync_get_refill_options, which an agent could easily confuse with a medication listing.

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?

"Choose current, discontinued or cancelled" gives parameter-level guidance but no when-to-use context, prerequisites, or routing to alternatives. The agent must infer that this is the right tool for viewing the med list versus requesting refills.

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