github_billing_delete_budget_org

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

No annotations are provided, and the description does not disclose any behavioral traits such as irreversibility, permission requirements, rate limits, or side effects. The description merely restates the obvious delete action without adding context.

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 very short and free of extraneous content, but it is too minimal. It could include a brief note on return behavior or typical use without becoming verbose.

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 description does not mention what happens after deletion (e.g., success status, response format). For a simple delete operation, the description should at least indicate that the resource is removed without return content.

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 100% schema description coverage, the schema already defines the parameters. The description adds no additional meaning about what 'org' or 'budget_id' represent or how to obtain the budget_id. Baseline 3 is appropriate as the description does not improve or clarify parameter semantics beyond the schema.

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 'Delete a budget for an organization' clearly states the action (delete) and the resource (budget for an org). It distinguishes itself from sibling tools like github_billing_get_budget_org and github_billing_update_budget_org, though it does not explicitly mention the GitHub billing API context.

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 no guidance on when to use this tool versus alternatives. Siblings like github_billing_get_budget_org and github_billing_update_budget_org exist, but the description does not clarify when deletion is appropriate or any prerequisites.

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