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

Annotations already provide readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context beyond that: it warns that ksao_type/canon_component_id are null by design and instructs the agent to interpret null as 'not yet joined' rather than 'no link.' This is valuable operational nuance not available from the annotations alone.

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 carry substantial information: the core purpose, three parameter-driven usage patterns, and a null-semantics caveat. There is no filler and the most important guidance 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?

Given a complex tool with 12 optional parameters, an output schema, and annotations, the description covers the essential conceptual model and key behavioral caveats. It does not explicitly map every parameter or provide a full worked example, but the schema fills those gaps, so the definition is reasonably complete for an agent to use it correctly.

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?

The schema already documents all 12 parameters with 100% coverage, so the baseline is 3. The description adds extra semantics for key parameters like min_guides, role, and capability_detail, including the hydrated-package behavior and null-handling guidance, which goes beyond the schema entries.

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 states a specific verb ('Traverse') and an explicit resource ('the capability spine') while enumerating the joined entity types: books, guides, KSAO elements, and jobs. This clearly separates it from sibling tools like get_guide or list_guides, which focus on a narrower resource.

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 explicit parameter-level use cases: min_guides=2 for cross-cutting capabilities, role=<role> for job requirements, and capability_detail=<slug> for hydrated packages. It does not explicitly contrast this tool with siblings or state when not to use it, so it stops short of a 5.

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