List private keys

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention the sensitive nature of private keys, clarify whether the actual key contents are returned or just metadata, or note any access requirements. The description is minimal and leaves these aspects ambiguous.

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 concise, front-loaded with the primary purpose, and each sentence adds context. The second sentence about key usage is relevant and earns its place, with no unnecessary details.

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 the simple tool, the description is still incomplete. It does not explain what the tool returns (e.g., key names vs. contents), address pagination, or clarify how it relates to createPrivateKey. With no output schema and no parameter descriptions, the description should provide more context for agents to use it correctly.

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 0%, so the description is expected to compensate for the lack of parameter documentation. However, it does not mention the 'limit' and 'offset' parameters or pagination behavior, adding no meaning beyond what the input schema already provides.

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 the tool's function with a specific verb and resource: 'List all SSH private keys.' It also adds context about how keys are used, distinguishing it from other list tools like listResources or listProjects.

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 implies usage by explaining that keys are used for server authentication and deploy keys, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. No sibling alternatives are mentioned.

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