atc_members

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

Annotations indicate read-only, idempotent, non-destructive, open-world. Description adds that RxNorm is US-centric but ATC codes are international, and explains source_atc_code usage for disambiguation. No contradictions with annotations.

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?

Description is well-structured with bullet points and clear statements. No wasted words, but could be slightly shorter without losing meaning. Front-loaded with primary purpose.

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 single parameter, rich annotations, and presence of output schema, the description covers all essential aspects: what it does, how to use it, behavioral notes, and limitations (US-centric catalog). Complete for its complexity.

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 defines atc_code with pattern but minimal description. Description adds critical behavioral semantics: higher levels (1-4) return all members, level 5 returns single substance. This provides value beyond schema.

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 lists drugs belonging to an ATC class, with examples like 'A10BA' returning metformin. It distinguishes from siblings such as atc_lookup and atc_classify by focusing on membership enumeration.

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?

Explicitly describes use cases (enumerate members, build drug lists, explore subtree) and notes that level 5 returns single substance. Does not explicitly contrast with alternatives, but context signals and sibling list make differentiation clear.

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