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

Annotations already signal read-only and non-destructive behavior. The description adds a valuable interpretive rule: 'ksao_type/canon_component_id are null by design where unresolved — treat null as not yet joined, never as no link.' This goes beyond the schema and prevents a likely misinterpretation of results. No contradiction with the annotations.

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 sentences, each earning its place: the core purpose, the key filter recipes, and the critical null-meaning caveat. The description is front-loaded with the traversal statement and contains no filler or redundancy.

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 complex 12-parameter traversal tool, the description provides the essential navigational patterns and the most important interpretation trap. The advanced filters such as conflicting, construct_class, and canon_promotion_candidate are left to the detailed schema, which is acceptable given the rich schema and output schema. An agent has enough context to select and invoke the 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 covers all 12 parameters at 100% with detailed, meaningful descriptions, so the description does not need to re-explain each parameter. The description does add example usage patterns, but these largely restate what the schema already conveys. Baseline 3 is appropriate when the schema does the heavy lifting.

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.' It identifies the resource and the relationships it navigates. It does not explicitly name sibling tools, but the traversal framing and the mention of packages, elements, and jobs distinguish it from a plain list or taxonomy fetch.

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 provides concrete, parameter-driven usage guidance: 'Use min_guides=2 for the cross-cutting capabilities... role=<role> for what a job requires, capability_detail=<slug> for one package with its elements and books hydrated.' This tells an agent which filter to reach for in common scenarios. It does not explicitly discuss when not to use the tool or alternatives, 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.