Create SSH Key

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

The description adds important behavioral details beyond annotations: 'The private key is stored in a hidden field and redacted in returned summaries.' This informs agents about security handling. Annotations only indicate it's not read-only and not destructive. No contradiction.

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 concise sentences: first states purpose, second provides usage and behavioral info. No wasted words, front-loaded with key information.

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 10 parameters and no output schema, the description covers purpose, usage, scoping, and a key behavior (private key hidden). It does not describe return values or error conditions, but the schema and annotations fill some gaps. Almost complete for a create tool.

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% with good parameter descriptions. The description adds high-level context about stored as a secure note and private key handling, but does not enhance individual parameter semantics beyond the schema. Baseline 3 is appropriate.

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 it creates an SSH key object stored as a secure note, and explicitly distinguishes it from login or payment card items, which differentiates it from siblings like keychain_create_login and keychain_create_card.

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 explicitly says 'Use this when you need a public/private key pair plus optional fingerprint or comment, not a login or payment card,' providing clear when-to-use and when-not-to-use guidance. It also mentions scoping support for folder, organization, and collection.

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