github_token_delete

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

Annotations already convey destructive intent (destructiveHint: true). The description adds valuable context: it states exactly what is removed (credential helper entry and RunBeacon profile reference) and the limitation regarding generic profiles. It does not mention potential remote effects (e.g., whether the PAT is revoked on GitHub), but given the annotation coverage, this is sufficient.

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 two sentences, front-loaded with the action, and every clause adds valuable information. No filler or redundancy.

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?

This is a simple one-parameter delete tool with annotations covering safety and a schema covering parameters. The description is complete for an agent to select and invoke it correctly, explaining the exact targets and the exclusion. No output schema exists, so no return-value explanation is needed.

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 schema already provides 100% coverage for the single parameter 'id' with description 'RunBeacon GitHub PAT profile to delete'. The tool description restates this in prose but adds no additional semantic meaning beyond what the schema provides. Baseline 3 applies.

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 action ('Delete a GitHub PAT created through github_token_save') and specifies the scope and mechanism ('from the configured Git credential helper and remove its RunBeacon profile reference'). It also distinguishes itself from generic deletions with the caveat 'This cannot delete generic OAuth/login profiles', making it distinct from sibling tools like credential_profile_delete.

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 scopes usage to GitHub PATs created via github_token_save, and explicitly excludes generic OAuth/login profiles, providing a clear when-not. It implies the correct alternative for generic profiles without naming a tool, but the boundary is unambiguous.

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