cloud_list_ssh_keys

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

With no annotations, the description provides some behavioral clues: 'Read only, free' indicates a safe, no-cost operation, and 'Compact by default' explains default output verbosity. However, it omits details like pagination, ordering, or potential errors, leaving gaps in understanding.

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 consists of three short sentences, each adding essential info: purpose, safety/free, and default behavior. No filler words; the most critical point comes first.

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 description covers basic purpose and constraints but lacks details on response format (what a 'compact' view includes), pagination, or handling of the 'query' parameter. For a simple list tool with no output schema, it is adequate but not fully comprehensive.

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%, so the schema already describes parameters. The description adds minimal value ('Compact by default' hints at the verbose parameter's default behavior) but does not extend meaning beyond schema descriptions.

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 'List SSH keys' clearly states the verb (List) and resource (SSH keys). The tool name matches and is distinct from sibling 'robot_list_ssh_keys', making the purpose 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 description lacks guidance on when to use this tool versus alternatives. It does not mention when to list all keys vs fetch a single one, nor does it contrast with siblings like 'robot_list_ssh_keys' or other listing tools. The 'Read only, free' hint is useful but not enough for decision-making.

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