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

Annotations already signal read-only/non-destructive behavior. The description adds meaningful behavioral context beyond that, especially the null semantics: 'ksao_type/canon_component_id are null by design... treat null as not yet joined, never as no link', plus the mode shift where capability_detail hydrates a package rather than querying elements. This is valuable non-obvious behavior the agent would not otherwise know.

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 three sentences with no filler: purpose first, then targeted parameter recipes, then a critical caveat about nulls. Every sentence earns its place and important information 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?

For a tool with 12 optional parameters and an output schema, the description covers the main query patterns, the null interpretation, and the special hydration mode. Combined with the fully documented schema and output schema, an agent has enough to call it correctly. A small gap is the lack of guidance on when this tool is preferable to sibling traversal tools.

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 and the schema already documents all 12 parameters. The description adds extra semantic guidance for min_guides, role, and capability_detail by showing which parameter to use for which analytical need, and it clarifies the meaning of null in output fields. That lifts it above baseline.

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 names a specific action ('Traverse the capability spine') and the resources joined (books, guides, KSAO elements, jobs), so an agent can tell what domain the tool operates on. It does not explicitly differentiate it from siblings like list_guides or list_taxonomy, which is why it does not earn a 5.

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 gives concrete, condition-triggered guidance: 'min_guides=2 for the cross-cutting capabilities', 'role=<role> for what a job requires', and 'capability_detail=<slug> for one package with its elements and books hydrated'. It does not mention when to prefer this tool over sibling tools or state exclusions, so it stops short of full when-to-use/when-not-to-use coverage.

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