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

Annotations already declare readOnly=false, idempotent=true, destructive=false and openWorld=false, but the description adds substantial behavior beyond them: reuse of existing entries, creation of provisional nodes only, belongs_to relationship creation, cycle rejection, and independent server-side structural validation ('client guidance cannot bypass this rule'). This is rich behavioral disclosure for a mutation tool.

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 usage constraint is front-loaded, but the body is a dense wall of text that repeatedly restates the same idea (naming variant vs. genuine concept, head-noun plus modifiers, attributes vs. types) across many sentences. Several sentences philosophize about classification semantics rather than describe the tool, and they do not earn their place.

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 mutating tool with a nested oneOf peer_decisions schema, 0% schema coverage and no output schema, the description covers creation/reuse/cycle behavior well, but says nothing about what the call returns (created nodes, aliases, resolution path). It is adequate but leaves the return contract entirely unspecified.

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 0%, so the description must carry parameter meaning, and it largely does: 'terms' is explained as a broad-to-specific verified path with the example ['food','recipe'], and 'peer_decisions' is described as either reusing an equivalent peer as one stable type with the wording registered as an alias, or justifying creation of a distinct type. It adds real meaning over the bare oneOf schema, though it never names the parameters directly.

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 concrete operation: submit a broad-to-specific path so the server reuses existing dictionary entries, creates only missing provisional nodes, adds belongs_to relationships and rejects cycles. This is a clear verb+resource with distinguishable function. It does not explicitly contrast itself against close siblings like resolve_subject_type or resolve_subject, so it falls short of 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 opening 'Use only after bounded root/child traversal provides enough evidence that the specific subject type does not yet exist' gives an explicit precondition for using this tool. It is a genuine when-to-use constraint, but it never names the alternative tools to use otherwise (e.g., resolve_subject_type, propose_subject_reclassification), leaving routing to inference.

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