gitea_delete_branch

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

With no annotations provided, the description carries the full burden. It discloses the important behavioral constraint regarding default branch protection, but omits other critical behavioral details like whether deletion is permanent, if it affects open pull requests, or required permissions.

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 appropriately brief with two sentences. The '[UNIFIED]' prefix is minor noise but doesn't significantly detract from the front-loaded action statement. No wasted words beyond that.

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 4 undocumented parameters and no output schema, the description is insufficient. It covers the core action but fails to document parameters, return behavior, or error cases that an agent would need to invoke this correctly.

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 input schema has 0% description coverage for its 4 required parameters (site, owner, repo, branch). The description mentions 'branch' implicitly but provides no semantic context for 'site', 'owner', or 'repo', failing to compensate for the schema's lack of documentation.

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 uses the specific verb 'Delete' with the resource 'branch from a Gitea repository' making the purpose clear. The constraint about the default branch adds useful specificity, though it doesn't explicitly distinguish from sibling tools like gitea_create_branch.

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 provides one usage constraint ('Cannot delete default branch'), indicating when the operation will fail. However, it lacks positive guidance on when to use this tool versus alternatives like archiving or merging branches.

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