get_class_hierarchy

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

No annotations exist; the description only states it returns hierarchy but lacks details on return format (e.g., list of names?), order, or potential performance impacts for deep hierarchies. Minimal disclosure beyond basic purpose.

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?

Single sentence, no redundancy. Perfectly 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?

Despite 3 parameters and no output schema, the description omits return format, potential errors, and usage constraints (e.g., whether max_depth applies equally to both directions). For an inheritance hierarchy tool, more behavioral context is needed.

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% with each parameter described. The description adds no new semantic meaning beyond the schema's parameter descriptions, so baseline score of 3 is appropriate.

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 retrieves inheritance hierarchy for a class, specifying ancestors, descendants, or both. This distinguishes it from siblings like 'analyze_class' or 'find_callers'.

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 implies use when class hierarchy is needed, but provides no explicit guidance on when to prefer this over siblings like 'analyze_class' that might also provide class information, nor any exclusions.

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