get_atc_classification

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that the operation is a lookup that returns WHO ATC hierarchy information, which hints at read-only behavior and return content, but it never states that no data is mutated, what happens when a drug name or RxCUI is not found, or whether multiple ATC codes can be returned.

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 short sentences with the action front-loaded and no filler. The second sentence adds some authority context (WHO) but is close to redundant with the first, keeping it just short of a 5.

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 one-parameter lookup with no output schema, the description covers the basic purpose and hints at the return content, but it omits any detail about the shape of the returned hierarchy or failure behavior. Adequate for a simple tool but with clear gaps an agent could hit.

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 100%, and the single parameter is fully documented in the schema as accepting a brand/generic name or RxCUI. The description only restates that same range ('given drug name or RxCUI'), adding no format, ambiguity-resolution, or matching-behavior detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Get ATC classification codes') and expands the ATC acronym, so the purpose is unambiguous. It does not differentiate itself from siblings like get_drug_ingredients or get_generic_name, but the operated-on resource (ATC hierarchy) is distinctive enough that misselection is unlikely.

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?

There is no when-to-use guidance, no statement of when an alternative sibling (e.g., get_drug_ingredients, get_generic_name) would be preferable, and no prerequisites or input-quality caveats. The agent must infer usage purely from the tool name.

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