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

Annotations only declare non-read-only and non-destructive, so the description carries real added weight: it names the exact authorities accepted (recorded operator identity, proven operator wallet, gateway admin) and enumerates failure semantics (403 for wrong identity, 401 for no credentials, 404 for an unregistered non-admin kernel). It also discloses the side effect of updating capability rows.

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 purpose and auth/error details are front-loaded and useful, but the closing sentence about WP-A and 'DECISIONS items 136 and 138' is internal process jargon that adds nothing for an agent selecting or invoking the tool.

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?

Behavioral and auth context is rich, and no output schema exists so return values are not required. However, with 0% param coverage and no return-shape hints, an agent still lacks enough to construct the capabilities payload confidently.

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 0% for both params, so the description must compensate and largely does not. It hints that capabilities are re-announced and that the kernel is identified, but gives no format, structure, or meaning for kernelId or the capability objects.

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 and resource: sending a heartbeat that re-announces capabilities and keeps the kernel alive while updating capability rows. This is clear, but it never distinguishes itself from the close siblings kernel_heartbeat and kernel_announce_capabilities, so an agent must guess which variant to pick.

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?

The authority prerequisites are spelled out in detail, which implies operational context, but there is no explicit when-to-use guidance and no routing away from kernel_heartbeat or kernel_announce_capabilities. Usage must be inferred from the purpose statement.

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