polypharmacy_risk_check_polypharmacy_risk

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

No annotations are provided, so the description should disclose behavioral traits. It does not mention whether the operation is read-only, if interactions are returned sorted or categorized, or any side effects. The description is too minimal to inform the agent about behavioral expectations.

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?

The description is a single concise sentence, but it lacks sufficient detail. It is front-loaded but fails to earn its place because it omits critical information that could be added without much bloat.

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?

Given the tool performs a complex check (polypharmacy risk) and has no output schema, the description should explain the output format (e.g., list of interactions, severity). It provides no information about return values or behavior, leaving a significant gap for an AI agent.

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 schema has 0% description coverage for the single parameter. The description adds no meaning about what format medication strings should take (e.g., names, codes), leaving the agent without guidance on how to populate the input correctly.

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 tool checks every pair of medications in a patient list for interaction risks, specifying the action and resource. It is specific enough to distinguish from some siblings, but does not explicitly differentiate from the similar 'orchestrator_check_drug_interactions' tool.

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?

No guidance is provided on when to use this tool versus alternatives, such as the sibling 'orchestrator_check_drug_interactions'. There is no indication of prerequisites or exclusions.

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