ssh_key_list

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

No annotations provided, so description carries full burden. It correctly indicates a read-only listing operation without destructive effects, but does not explicitly state it is non-destructive or disclose behavior like missing directory or encrypted keys. Adequate but not exhaustive.

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 sentences: first defines the action, second gives usage guidance. No unnecessary words, front-loaded, every sentence adds value.

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?

No output schema, but description explains return fields (type, fingerprint, loaded status) and target directory (~/.ssh/). For a simple list tool, this fully covers what the agent needs to know about the output and scope.

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?

Tool has zero parameters, and schema description coverage is 100%. Baseline score of 4 applies as description does not need to add parameter info.

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?

Description clearly states specific verb 'list', resource 'SSH private keys in ~/.ssh/', and details returned information (type, fingerprint, loaded status). It distinguishes from siblings like ssh_key_load by explicitly noting it shows which keys need to be loaded.

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?

Second sentence provides clear context: 'Use this to find which keys are available and which ones need to be loaded.' This implies when to use before loading. However, it does not explicitly mention when not to use or alternatives, though siblings cover other operations.

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