github_repos_delete_deploy_key

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. While 'Delete' implies a destructive, irreversible action, the description does not explicitly state that the operation is permanent or highlight any required authorization, leaving the agent to infer these critical details.

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 extremely concise at one sentence, front-loading the core action. Every word serves a purpose, though it could afford a bit more detail without sacrificing conciseness.

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 simplicity of the operation, the description covers the basic action but lacks completeness. It omits important context such as the requirement for admin/push permissions, the fact that the key must exist, and potential error scenarios. With no output schema, the agent also gets no information about return values or success/failure indications.

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?

The input schema's parameter descriptions are minimal (just 'owner', 'repo', 'key_id'), and the tool description adds no additional meaning. The agent cannot discern from the description alone that 'key_id' refers to the deploy key's numeric ID, which is essential for correct invocation.

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 verb 'Delete' and the resource 'deploy key', making the tool's function unambiguous. It distinguishes itself from sibling tools like 'create_deploy_key', 'get_deploy_key', and 'list_deploy_keys' by specifying the delete action.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., required permissions) or context for appropriate usage. This lack of contextual advice reduces its utility for an AI agent deciding between related tools.

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