github_delete_branch_ref

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

The description does not disclose the destructive nature of the operation, permission requirements, or behavior on non-existent refs. Since no annotations are provided, the description carries full burden but fails to address behavioral traits beyond routing and auth scope.

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 (three sentences) and efficiently communicates the tool's identity and routing. However, it is too sparse to be fully informative, but that is a completeness issue, not a conciseness issue.

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 that this is a destructive GitHub operation, the description lacks essential context such as typical usage scenarios, error states (e.g., branch not found), or relationship with other GitHub tools. The existence of an output schema slightly mitigates the need for return value documentation, but overall the description is incomplete for an agent to use effectively.

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 single parameter 'arguments' is described only as 'JSON string of arguments for the connector operation', which adds no meaning beyond the schema. With 0% schema description coverage, the description does not specify expected keys or structure for the JSON, leaving the agent without guidance on how to construct the input.

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_branch_ref' and identifies it as a GitHub connector operation, indicating it deletes a branch reference. However, it lacks specificity about what exactly 'branch ref' means and does not differentiate from sibling tools like github_create_branch_ref or github_get_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?

No guidance is provided on when to use this tool versus alternatives (e.g., github_create_branch_ref, github_get_branch). The description does not mention prerequisites, typical use cases, or when not to use it.

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