Github Api Delete

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds real context beyond that: 'Neither can be undone' and 'GitHub decides what the token may remove', which tells the agent the outcome depends on token scope rather than the tool. It does not cover error behavior or rate limits, which keeps it from a 5.

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 irreversibility warning and the token-scope caveat are front-loaded and earn their place. 'See #543' is a dangling reference with no meaning to an agent, and appending the skill pointer as a trailing 'Workflow and conventions' line is slightly wasteful but still useful.

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?

An output schema exists and annotations carry the destructive/non-idempotent profile, so the description only needs to cover intent and risk, which it does. Minor gaps are the relationship between the path and graphql parameters and what failure looks like when the token lacks permission.

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%, so every parameter already carries a description, and the baseline is 3. The description adds the framing that there are two modes (path-DELETE vs GraphQL mutation), which helps the agent pick between the path/graphql/variables parameters, but it does not clarify mutual exclusivity or defaults.

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?

States a specific verb and resource: a raw DELETE to any path under api.github.com, or a GraphQL mutation that removes something. The phrase 'for a removal no other tool makes' implicitly separates it from dedicated siblings like github_delete_branch, github_delete_release, and github_delete_tag, though it never names them.

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?

'for a removal no other tool makes' gives a clear selection rule against the dedicated delete tools, and 'Workflow and conventions: github_get_skill("api-requests")' points to required setup knowledge. It stops short of explicit when-not guidance, such as warning that branch/release/tag deletion should go to the specialized tools.

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