github_delete_branch

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

The description only states the action without disclosing behavioral traits such as permanence of deletion, failure conditions for protected or default branches, or effects on open pull requests. Since no annotations are provided, the description carries the full burden and does not address these safety or side-effect aspects.

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 concise, front-loaded with the core action, and has a simple structured argument list. It wastes no words, though it sacrifices depth for brevity. For such a simple tool, the length is appropriate, but it could use the space to add nuance.

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?

The tool is a simple delete operation, but the description omits important context like restrictions (protected/default branches) and what happens after deletion. The output schema exists, so return values are avoided, but the description does not fully cover the operation's context given no annotations and a 0% schema description coverage.

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 description lists parameters with terse one-liners like 'owner: Repository owner' and 'repo: Repository name', which add minimal meaning beyond the parameter names in the schema. The schema itself has no descriptions, so the description should compensate but does not provide meaningful detail, especially for 'session_name' which is only described as 'GitHub session to use'.

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 'Delete a branch from a repository.' This uses a specific verb and resource, and distinguishes this tool from sibling branch tools like list, get, create, and protect. It is immediately obvious what action is performed.

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 provided on when to use this tool versus alternatives. It does not mention that this only deletes a branch, not the repository, nor does it note any restrictions like protected branches or default branch limitations. There is no context about prerequisites or preferred invocation scenarios.

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