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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful context beyond them: callers learn the endpoint is public, that the slug is non-secret, and that channel credentialRef values are vault references rather than credentials — relevant for an agent deciding whether the call is safe. It does not discuss rate limits or pagination.

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?

Three dense sentences, front-loaded with what the tool returns and followed by usage and privacy notes. Nearly every clause earns its place, though the parenthetical about credentialRef is slightly tangential to 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?

With no output schema, the description carries the return-shape burden and does so adequately: totals, a `missing` list, and status values ready|partial|unconfigured. For a one-parameter read tool this is nearly complete, with only pagination/format detail left unspecified.

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% and the single parameter is fully documented, so the baseline is 3. The description adds meaning beyond the schema by characterizing the slug as non-secret (typically a wallet address), which affects an agent's handling decisions.

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?

Names a specific verb+resource ('four-slot substrate view for an operator') and enumerates exactly what the four slots are: kernels, capabilities with sla/availability, notification channels, and per-kernel A2A agent-card URLs. The scope is narrow enough that an agent can distinguish it from get_operator_dashboard, get_operator_certs, and list_operator_channels without opening the schema.

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 states the situation for use: 'from an onboarding agent's wrap-up step to confirm are all four slots wired before I go live.' That is a clear context, but no alternative sibling (e.g., a dashboard or certs tool) is named or excluded, so it stops short of full routing guidance.

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