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

Annotations already indicate it is not read-only and not destructive. The description adds valuable behavioral constraints: it never funds jobs or exposes signer/token secrets, and it explicitly manages one-time auth and the fleet. This goes beyond the annotation flags and clarifies side effects and security posture, though it does not detail per-action behavior.

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 three short sentences with zero filler. It front-loads the admin restriction and core purpose, then adds a critical safety constraint. Every sentence earns its place.

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?

The output schema covers return values, and the parameter schema explains each action and its requirements (e.g., request_id for complete_auth). The description gives the overall scope and constraints, but it does not explain the sequential flow (e.g., start_auth then complete_auth) or prerequisites. For a multi-action admin tool, a brief note on the auth workflow would enhance completeness, but it is still adequate given the schema richness.

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 four parameters have clear descriptions in the schema. The tool description adds no extra parameter semantics. Given the high schema coverage, the baseline of 3 is appropriate; the description does not need to repeat parameter details.

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 clearly states a specific verb ('manages'), the resource ('Virtuals auth and the complete six-offering AlpineLead Field Agent fleet'), and the admin-only scope. It also distinguishes itself from the many sibling tools by naming its exact domain, and the constraint 'Never funds jobs or exposes signer/token secrets' adds specificity.

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 description provides clear context: it is for owner/admin only and covers auth and fleet setup. However, it does not explicitly mention when to choose this over alternatives or when not to use it. The context is sufficient to infer usage, but no exclusions or sibling routing are given.

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