wxoGetDrugAlternativeTreatments

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

No annotations are provided, so the description carries the burden of disclosing behavior. It only states that it 'retrieves information,' implying a read-only operation, but does not mention return format, error behavior, or whether 'None' means no results. The phrase 'or None' hints at a possible return value but is not elaborated.

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 sentence with no fluff, making it highly concise. However, the placement of 'or None' creates an awkward grammatical structure that slightly harms readability.

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 no usage guidance and minimal behavioral disclosure, the description is incomplete for a tool that has multiple siblings and an ambiguous return statement. It does not explain what constitutes an 'alternative treatment' or how results are presented, making it insufficient for an agent to confidently invoke this tool.

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 description says 'for a given drug,' which clarifies that the drug_name parameter refers to the drug for which alternatives are sought. This adds some meaning beyond the schema, but it does not detail expected format or behavior when the drug is not found. Since schema coverage is 0%, this minimal clarification gives a baseline score of 3.

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 identifies the tool's function: 'Retrieves information about alternative treatments for a given drug.' This distinguishes it from sibling tools like wxoGetDrugInterations and wxoGetDrugContraindications. However, the suffix 'or None' is ambiguous and could confuse readers about whether the tool returns None or accepts None.

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. With multiple drug-related siblings, the description should clarify that this is for alternative treatment options, but it does not. There is no mention of prerequisites or expected use cases.

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