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

Annotations already declare non-read-only, open-world, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds that the effect is a persistent entry in a shared 'global peer table', but says nothing about what validation occurs, whether re-registering overwrites an existing node, or what the open-world fetch of manifestUrl entails — gaps that matter for an openWorldHint=rue mutation.

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?

A single front-loaded sentence with no trailing filler, which is appropriately sized for this operation. The jargon stack ('DRP v1.0 / MCP', 'Distributed Resistance') costs some clarity but does not bloat the text.

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?

An output schema exists, so return values need no explanation here, and the schema covers all inputs. Still, for a registration tool whose only required inputs are domain and API key, the description never states what makes a domain eligible or what the called tool will attempt to fetch from it, leaving the agent to guess at failure modes.

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%, so all five parameters (including the kf_ext_/kf_core_ key format) are already documented in the schema. The description contributes no additional parameter meaning, 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?

The description names a specific verb ('Interlink') and resource ('external sovereign web domain running an AI agent node') with a clear target ('global peer table'). It implicitly distinguishes itself from the sibling kinform_register_agent (agent vs. domain node), though that contrast is never made explicit and the branding-heavy phrasing ('Distributed Resistance') adds fog rather than precision.

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?

There is no statement of when to use this tool versus alternatives — notably kinform_register_agent, which shares an API-key dependency and an obvious overlap in purpose. No prerequisites, eligibility conditions, or exclusions are given; the agent must infer usage entirely from the name and schema.

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