delete_repo

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

With no annotations, the description carries the full burden of disclosure, but 'Delete a repository.' reveals nothing about the irreversibility, permission requirements, or cascading effects of repository deletion. For a destructive GitHub operation, this omission is significant.

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 short and front-loaded, but brevity is the only virtue. It under-specifies behavior and parameters, so this is under-specification rather than effective 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?

For a destructive operation with no annotations and no parameter documentation, the description is incomplete. Even though an output schema may exist, an agent cannot safely invoke this tool without knowing that repository deletion is permanent and what prerequisites apply.

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?

Input schema has 0% description coverage and the description adds no parameter meaning. Both 'owner' and 'repo' appear only as names/titles, and the description does not clarify their format, relationship, or required values.

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 states a specific verb ('Delete') and a specific resource ('a repository'), clearly distinguishing it from sibling file/branch/comment deletion tools at a basic level. However, it does not explicitly differentiate itself from alternatives or add scope constraints, so it stops short of a 5.

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?

No guidance is given about when to use this tool versus alternative deletion tools such as delete_file, delete_branch, or delete_issue_comment. There are no prerequisites, ownership conditions, or examples, so an agent must infer suitability from the name alone.

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