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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by revealing that the payload includes sensitive material (model keys, SSH keys) and the caller's permission scope, but it says nothing about output shape, freshness, or whether credentials are redacted.

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 sentence, front-loaded with the resource ('The bootkey account') and then a tight inventory of what comes back. No filler, no repetition, easy to scan.

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 parameters and no output schema, the description takes on the job of describing the return payload, and it does so more thoroughly than most. It falls short only on structural details (format, nesting, ordering) that an agent might want before parsing the response.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument, whole-account read rather than a filtered query, which matches the empty 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 enumerates exactly what the call returns: balance, boot prerequisites, connected model keys, SSH keys, every agent with status, and this connection's permissions. That is concrete enough to distinguish it from get_agent (single agent) and get_options, though it never uses an explicit verb like 'returns' and leaves the contrast with siblings implicit.

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 explicit when-to-use or when-not-to-use statement and no named alternative. The phrase 'what booting another agent needs' hints that this is a pre-flight check before boot_agent, which is a useful implied usage cue, but the agent must infer it.

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