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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds that each child comes back with its title, but omits result-size expectations, empty-result behavior for leaf nodes, and how the version parameter affects results.

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 sentences, zero padding: the first defines the operation and its hierarchy, the second gives the input constraint. The core action is front-loaded.

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 output schema, the description carries the return-shape burden and does so adequately by mentioning child titles. A brief note on empty results for leaf symbols or version defaults would make it complete for a hierarchical drill-down 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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by mapping input type to output granularity — a subclass yields main groups, a group yields subgroups — which explains why the two example forms differ. It still says nothing about the version parameter beyond what the schema documents.

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 ("List the IPC symbols directly classified under one IPC symbol") and explains the hierarchy levels it returns (main groups under a subclass, subgroups under a group). It does not explicitly contrast itself with siblings such as ipc_lookup or ipc_search, so the distinction must be inferred.

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 constrains the accepted input shape (subclass "A01N" or group "A61K 31/00"), which implies when this drill-down is appropriate. However, it never states when to use this instead of ipc_search or ipc_lookup, nor what to do with leaf symbols that have no children.

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