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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds crucial context beyond annotations: the one-time reveal is not spent until a password is returned, pending state behavior, timing, and that the response matches get_vps_status plus the password. No contradiction with annotations.

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 with the core behavior and well-organized, but it is somewhat verbose and repeats key points (e.g., 'call again in 30-60 s' and 'reset_password') in both the main text and the typical-scenario summary. Every sentence adds value, but trimming would improve conciseness.

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?

Given no output schema and the complexity of a one-time secret reveal, the description is complete: it covers prerequisites (token, keyless VPS), return format (same as get_vps_status plus password), pending state, and recovery via reset_password.

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% for the single optional service_id parameter. The description does not add any parameter-specific meaning beyond what the schema already provides, so the baseline of 3 applies.

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 states a specific verb and resource: 'Read the root (Windows: Administrator) password of a keyless VPS'. It distinguishes the tool from siblings like reset_password and set_password by explaining the one-time reveal nature and the keyless requirement.

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?

Explicit when-to-use guidance is given: call again in 30-60s if password_pending, use reset_password if the password is lost, and no password is needed if an SSH key was ordered. Alternatives and exclusions are clearly named.

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