cloud_list_ssh_keys

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

The description mentions no behavioral traits. There are no annotations (readOnlyHint, etc.) and the description does not disclose whether the operation is read-only, paginated, sorted, or if it requires any permissions. This is a significant gap for a list tool.

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 a single short sentence, which is concise but overly terse. It could be expanded with essential details without losing conciseness. It is appropriately front-loaded but lacks substance.

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 5 parameters, an output schema, and many sibling tools, the description is woefully incomplete. It does not mention that results can be filtered by name, fingerprint, or label selector, nor does it cover pagination (page/per_page) or the structure of the response. Users need to infer everything from schema alone.

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?

With 0% schema description coverage, the description should explain what the parameters (page, per_page, name, fingerprint, label_selector) are for. It adds no information beyond the parameter names, which are somewhat self-explanatory but still insufficient without context on filtering behavior.

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 in the project' clearly indicates the verb (list) and resource (SSH keys), but does not specify scope ('all' vs filtered) or distinguish from sibling tools like 'cloud_get_ssh_key' which retrieves a single key. It's adequate but lacks differentiation.

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?

No guidance is provided on when to use this tool versus alternatives, such as using 'cloud_get_ssh_key' for a single key or other list tools. There is no mention of context, prerequisites, or why one might prefer this over others.

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