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

Annotations only give destructiveHint=true; the description goes well beyond them, disclosing that the operation passes branch protection, rulesets and secret scan like a push, and that it fires CI/webhooks. It also names the required auth scope, which is exactly the behavioral context an agent needs for a destructive mutation.

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?

Three dense sentences with the action and mechanism front-loaded, followed by requirements and side effects. No filler, every clause earns its place.

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?

No output schema exists and the tool is a destructive mutation, so the description must stand alone; it covers side effects, auth scope and the API mapping well. It could still say what happens on a stale/mismatched sha or describe the failure response, which is the only notable gap.

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?

Schema description coverage is only 17% (just sha), so the description must carry the load. It usefully explains the sha as the 'existing blob sha' for optimistic concurrency, but leaves owner/repo/path/branch/message entirely unexplained, so it only partially compensates for the coverage gap.

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?

States a specific verb+resource ('Delete a file from a branch') and adds the mechanism ('via git plumbing') plus the API equivalent ('Mirrors DELETE /api/v2/contents'). This clearly distinguishes it from siblings like gluecron_delete_repo and gluecron_write_file without needing to open a schema.

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 concrete preconditions: the existing blob sha (optimistic concurrency) and 'repo' scope are required. It does not, however, explicitly name when to prefer an alternative (e.g., apply_patch or write_file) or state exclusions, so it stops short of full when/when-not guidance.

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