gitea_delete_file

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

No annotations provided, so description carries full burden. Adds valuable behavioral context about 'conflict detection' mechanism via SHA requirement. However, misses irreversibility warning, auth requirements, or failure modes expected for a destructive operation.

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 efficient sentences with critical information front-loaded after the '[UNIFIED]' tag. No redundant text, though the prefix tag provides marginal value. Second sentence strategically places the critical SHA constraint.

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?

Given 7 parameters with zero schema documentation and no output schema, description provides minimum viable coverage by explaining the core action and SHA requirement. However, significant gaps remain for a destructive operation with this many undocumented parameters.

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?

With 0% schema description coverage, description fails to compensate adequately for 7 parameters. Only explicitly documents the 'sha' parameter ('Requires current file SHA'). Leaves site, owner, repo, message, branch, and path completely unexplained despite high parameter count.

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 clearly states 'Delete a file from a Gitea repository' with specific verb (Delete) and resource (file). The action distinctly differs from sibling tools like gitea_create_file and gitea_update_file.

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 implied usage guidance by stating SHA requirement ('Requires current file SHA'), indicating a prerequisite for use. However, lacks explicit when-to-use/when-not-to-use guidance or comparison to alternatives like gitea_update_file.

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