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

Annotations only say readOnlyHint=false and destructiveHint=false; the description provides substantial extra behavior: it advances the node's liveness clock separately from operator standing, fails closed on bad/absent/replayed signatures or stale timestamps, and describes both success and error returns. This goes far beyond the structured annotation data.

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 description is front-loaded and dense with important information, but it is written as one long paragraph with a cryptic 'CO 486' reference and an example that says to call with arguments {} despite five required parameters. That example is misleading and the overall structure could be more scannable.

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 security-sensitive tool with no output schema, the description is complete: it covers auth expectations, side effects, failure modes, and both success and error return shapes. The schema handles parameter vocabulary, while the description covers operational context such as liveness-clock separation and why replay/stale timestamps fail.

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 100%, so the schema already documents all parameters. The description adds value by explaining the canonical signed envelope, the single-use nature of the nonce, timestamp skew, and how the signature and algorithm relate to the bound key. A minor inconsistency is mentioning 'route' in the envelope while no route parameter appears in the 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 description opens with a concrete action: a self-hosted node reports in to the hub on its own initiative, and it immediately disambiguates the interaction model ('the hub never calls the node'). It also clarifies the auth distinction (NODE-SIGNED vs operator-token'd), making the tool's role clear against sibling federation tools.

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 clear triggering context: node-initiated, poll-shaped reporting where the hub does not initiate, and no operator token is required because the signature is the auth. It does not explicitly name alternatives or provide when-not-to-use exclusions, but the conditions are unambiguous enough for an agent to route correctly.

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