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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), but the description adds real value beyond them: the required permission scope (ssh_keys:read) and the account prerequisite (free GPU Cloud account plus MCP key). It stops short of describing pagination or return shape.

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?

Two short bracketed fragments, front-loaded with the resource. Every clause carries information (resource, purpose, permission, prerequisite), though the stacked parentheses are slightly clunky to read.

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?

For a zero-parameter, read-only list tool with no output schema, the description covers what is listed, why the keys exist, the auth scope, and the account requirement. Nothing essential to calling it correctly is missing.

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 zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies per the rules.

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 resource — the account's SSH public keys — and adds parenthetical context that these keys are used to access new servers. The verb is implied rather than stated (it comes from the name), and it doesn't explicitly distinguish itself from add_ssh_key, delete_ssh_key, or generate_ssh_key, but the resource is unambiguous.

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 clause 'used to access new servers' hints at why the keys matter, but there is no explicit when-to-use guidance or routing against the sibling ssh-key tools (add/delete/generate). Usage is only implied.

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