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

The description states the operation is a read/traversal ('read through the predicate registry'), while the annotations declare readOnlyHint=false and destructiveHint=true. This is a direct conflict about the tool's safety profile, so no amount of extra detail (inverse/symmetric predicate handling, ordering, no de-duplication) can be credited as consistent transparency.

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 core purpose is front-loaded and almost every clause carries operational information (ordering rules, no de-duplication, supersededBy caveat), so there is little waste. However, the middle sentences are dense run-ons packed with parentheticals, which makes the block harder to scan than it needs to be.

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?

There is no output schema, so the description carries the return-value burden itself, and it does: ordering by timestamp then relation id, the untimestamped tool-recorded edges, and the 'not de-duplicated' caveat. For a two-parameter traversal tool this is complete enough to call 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 coverage is already 100%, but the description adds substantial meaning beyond it: predicate semantics for inverse names (read backwards), symmetric predicates (related, closeMatch, both directions), legacy free-form names answered from stored edges, and the special id+hasMember collection case. This is well above the baseline for a fully documented 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 first clause gives a specific verb+resource ('one-hop traversal from an entity, read through the predicate registry') and the description explicitly distinguishes itself from siblings such as sim_edges ('sim_edges lists the edge's witnesses') and implicitly from multi-hop tools. An agent can tell exactly what graph operation this performs.

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?

It gives strong usage conditions: omit predicate for all outgoing relations, pass predicate to restrict, use hasMember with a collection id to list members, and unknown names are refused. It never explicitly names an alternative for multi-hop traversal (e.g. sim_reach), so the sibling routing is only partial.

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