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

Annotations already mark the tool as read-only and non-destructive, but the description adds important behavioral nuance beyond that: 'ksao_type/canon_component_id are null by design where unresolved — treat null as not yet joined, never as no link.' This prevents a common misreading and gives the agent essential interpretation guidance.

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. Each sentence earns its place: the first defines the tool's scope, the second gives high-value parameter use cases, and the third explains the crucial null-handling convention. It is front-loaded and easily scannable.

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 12 optional parameters, 100% schema coverage, an output schema, and read-only annotations, the description covers the remaining gaps well by highlighting key usage patterns and the null semantics that the schema alone would not convey. An agent has enough context to select and call this tool 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 input schema already documents all 12 parameters with high coverage, so the baseline is 3. The description adds extra semantic value by explaining what specific parameter combinations are for, such as min_guides=2 for cross-cutting capabilities and capability_detail for hydrated package output, going slightly beyond the schema.

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 opens with a specific verb and resource: 'Traverse the capability spine joining books, guides, KSAO-grade elements and jobs.' This makes the tool's scope immediately clear and sets it apart from siblings like get_guide and list_guides, which focus on single guides or listing guides rather than cross-entity traversal.

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 usage patterns: 'Use 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.' This is actionable guidance, though it does not explicitly state when not to use this tool versus the sibling tools.

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