delete_bill

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the delete operation itself and never mentions irreversibility, cascading effects on related resources (e.g., transactions or attachments), permission requirements, or what happens when the delete fails.

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 sentence is maximally short and front-loaded with the action, which is structurally good. But conciseness here is achieved by omitting substance; almost all of the description's content is already present in the tool name itself.

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 tool with no annotations and no output schema, a single bare phrase is inadequate. An agent needs at least a statement of side effects, reversibility, or preconditions, none of which is present.

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 0% for the single required 'id' parameter, and the description does not compensate. That 'id' refers to the bill to delete is inferable from context, but no information is given about ID format, whether it is stable or user-facing, or relationships to other resources.

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 states a clear verb ('Delete') and resource ('a bill'), so an agent can tell this is the deletion counterpart to list_bills/create_bill. However, it essentially restates the tool name verbatim and adds nothing about scope or specifics beyond that.

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?

There is no guidance on when to use this tool versus alternatives, no preconditions (e.g., bill must exist first), and no indication of when deletion is not appropriate. The description gives zero context for selection among the many CRUD siblings.

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