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

With no annotations, the description carries the full burden; it usefully discloses the return shape (text, kernel insight, principles, outgoing connections with asymmetric bridge descriptions), which substitutes for the missing output schema. However it says nothing about permissions, failure modes, or size/cost of the response.

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 dense, front-loaded sentences with no filler; the payload contents are listed first and the usage cue follows. Slightly list-heavy but every clause carries information.

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 single-id lookup with 100% schema coverage, the main gap is the absent output schema, which the description largely compensates for by enumerating what is returned. It stops short of describing bridge semantics or edge cases, but an agent has enough to call 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?

Schema description coverage is 100% and the id param carries its own format example ('the_ratchet'), so the schema does the heavy lifting. The description adds no extra constraint or format meaning for the parameter, so the baseline 3 applies.

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?

States a specific verb (Get) and resource (a single piece) and enumerates the returned payload (plain text, kernel insight, principles, outgoing connections). It is clearly distinguishable from the plural/connection-focused siblings by the word 'single', though it never names an alternative tool explicitly.

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?

'Use this to read a piece and understand its connections' gives an implied context, but the sibling set contains overlapping tools (read, get_connections, navigate, traverse) and the description never says when to pick this over them. Usage is inferred rather than stated.

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