get_medications

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds the meaningful scoping trait that only medications with status='taking' are returned, but says nothing about ordering, recency, or whether historical meds are excluded outright.

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?

A single front-loaded sentence carrying verb, resource, payload, and filter with zero waste. Nothing extraneous and the key constraint is stated immediately.

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, return values need not be explained, and for a zero-param read tool this is nearly sufficient. The only residual gap is a lack of routing context against the many sibling read tools.

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 the baseline is 4. The description's parenthetical restates the only implicit input concept (status='taking'), but no parameter semantics are actually needed here.

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+resource ('get_medications') plus explicit scope: current medications with doses filtered to status='taking'. An agent can distinguish it from the write-side sibling record_medication. It does not, however, explicitly differentiate itself from check_medication_safety or get_allergies.

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?

The filter condition (status='taking') implies when this returns data, but there is no explicit guidance on when to prefer this over siblings such as check_medication_safety or get_health_summary, and no exclusions stated. Usage is inferable but not spelled out.

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