Add a medication

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

The description discloses critical behavioral traits beyond the annotations: 'The medication is always added' signals non-idempotent, always-effective behavior, and it goes further by explaining that the result carries interaction/allergy warnings and instructing the agent to read them aloud. This is rich, actionable context.

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 tight sentences with no filler. The primary action is front-loaded, followed by essential behavioral caveats. Every sentence 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 12-parameter tool with an output schema and annotations, the description provides the missing context: side-effect certainty, warning-reading obligations, and medical disclaimer. An agent has enough to select and invoke the tool correctly.

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 92%, so the schema already documents parameter meaning. The description adds no parameter-specific guidance beyond the general medication concept, which is appropriate but not above the baseline.

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 clearly states the action ('adds a medication') and the resource ('the elder's schedule'), and attributes it to a caregiver. It is distinct from sibling tools like log_dose or skip_dose, which handle existing doses rather than adding new medications.

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 description establishes clear usage context: this is the tool for a caregiver to add a medication to the schedule. It does not explicitly name when-not-to-use or alternatives, but its role is self-evident against the sibling list.

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