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

The description discloses a critical interpretation rule — ksao_type/canon_component_id nulls are 'not yet joined', never 'no link' — which prevents a plausible misreading of results. Annotations already carry the safety profile (readOnlyHint=true, destructiveHint=false), and the description is fully consistent with them, adding interpretive context beyond what annotations provide.

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?

Three dense sentences with the purpose front-loaded and no filler. The middle sentence packs three usage recipes compactly, which is readable despite its density; every sentence earns its place, including the null-semantics warning.

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 12-parameter, 0-required tool with an output schema and 100% schema coverage, the description supplies the unifying conceptual model — the spine join across books, guides, elements, and jobs — plus the critical null-handling rule. The only notable gap is the absence of explicit routing to sibling tools (get_guide, list_guides, list_taxonomy).

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% with rich per-parameter text (e.g., the 95.1% validation note on ksao_type and the ~30% person-attribute note on construct_class), so the baseline is 3. The description's references to min_guides, role, and capability_detail largely restate the schema rather than adding new meaning.

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 action — 'Traverse the capability spine joining books, guides (capability packages), KSAO-grade elements and jobs' — with a clear resource and scope that distinguishes it from the simpler list/get siblings. It doesn't name a sibling explicitly, so differentiation from get_guide, list_guides, and list_taxonomy is implied rather than stated.

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?

Three concrete usage recipes are provided: min_guides=2 for cross-cutting capabilities, role= for what a job requires, and capability_detail= for a single hydrated package. This gives an agent clear entry points by scenario, though it never states when to prefer a sibling tool such as list_guides over this one.

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