delete_repository

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

Informs about required scope and confirmation parameter. With no annotations, this is good coverage, though it could also mention irreversibility or effects on collaborators.

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 sentences, front-loaded with core purpose, followed by essential conditions. No wasted words.

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?

Adequately covers purpose, scope, and confirm requirement. Missing: behavior when confirm=false, and clarification on optional owner parameter. Overall sufficient for a simple 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?

Only mentions confirm parameter indirectly ('requires confirm=true'), but does not clarify the roles of owner and repo. Schema coverage is 0%, so description should compensate more.

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?

Description explicitly states 'Delete a GitHub repository'. The verb and resource are clear, distinguishing it from sibling tools like add_repository_labels or list_repositories.

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?

Provides clear usage conditions: requires confirm=true and PAT with 'delete_repo' scope. Does not explicitly mention when not to use, but the purpose is sufficiently self-explanatory.

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