relay_get_impact

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

No annotations provided, so the description carries the burden. It discloses read semantics and that results carry distances, but says nothing about permissions, result limits, traversal depth, or behavior on cycles/missing facts.

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 tight sentences: what it returns first, then when to use it. Zero wasted words.

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 simple one-param read tool with no output schema, the description conveys purpose, semantics (direct/indirect with distance), and usage well. Minor gap: no note on output shape or traversal limits, but the core is complete.

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?

Single required uuid fact_id with 0% schema description coverage. The description implies the parameter is the root fact for the traversal, which is helpful, but doesn't state format or edge cases beyond the schema's uuid type.

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 (list) and resource (facts built on top of the given fact, directly or indirectly) with distance, and distinguishes it clearly from siblings like relay_save_fact or relay_get_context.

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?

Explicitly directs use before changing or reversing a decision to see what else depends on it — a clear when-to-use with a concrete scenario. Alternatives aren't named, but the use condition is specific and unambiguous.

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