wxoGetDrugContraindications

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

With no annotations, the description carries the full burden of disclosing behavior. It only discloses that it returns information or None, which suggests a read-only query. It does not specify conditions for None, error handling, authentication, or rate limits. This is minimal transparency.

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 one sentence, front-loaded, and contains no fluff. It includes a typo ('inforamation') and the word 'comprehensive' adds little but does not detract significantly. Overall, it is appropriately concise.

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?

The tool is simple with one parameter and an output schema. The description covers the core purpose and return possibility, but lacks usage distinction from siblings and behavioral details. It is adequate for a basic query but leaves the agent to infer when to use it.

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 0%, so the description must compensate for documenting the parameter. It only says 'for a given drug', which refers to drug_name but does not define format, accepted values, or required syntax. It adds little beyond the schema's property title.

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 returns drug contraindication information for a given drug. It uses a specific verb ('Returns') and resource, and the mention of 'or None' clarifies the return. It distinguishes from sibling tools like wxoGetDrugInterations and wxoGetDrugInformation by focusing on contraindications specifically.

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 provides no explicit guidance on when to use this tool versus alternatives. 'For a given drug' implies a drug-related query, but there is no mention of alternatives or exclusions. Usage is implied rather than explicitly stated.

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