manage_gpg_keys

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the tool modifies GPG keys (add/delete). The description does not disclose side effects, authentication requirements, or constraints (e.g., impact on existing keys). For a mutation tool, more behavioral context is expected.

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 with one sentence and an actions list. It front-loads the purpose. Slightly more structure (e.g., bullet points) could improve readability, but it is efficient.

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 tool is simple (add/delete GPG key), but the description lacks information on return values, authorization, or limits. Given no output schema, the agent would benefit from knowing what happens on success/failure. It is adequate but not 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%, providing baseline. The description adds clarifications: 'add a key' for 'add', 'remove a key' for 'delete', and notes that 'text' is required for add and 'keyId' for delete. This adds value beyond the schema's property 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 clearly states the tool manages GPG keys for the authenticated user and lists the available actions (add, delete). It distinguishes from sibling tools like list_gpg_keys (for listing) and manage_ssh_keys (for SSH keys). However, it could be more specific about the scope.

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 for adding/deleting GPG keys, but provides no explicit guidance on when to choose this tool over alternatives (e.g., list_gpg_keys for viewing). No exclusions or prerequisites are mentioned.

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