delete_bill

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. However, the description adds no extra behavioral context such as whether deletion is permanent, cascading, or if there are restrictions on which bills can be deleted. The openWorldHint suggests potential side effects, but the description does not explain them.

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 a single, minimal sentence that conveys the purpose without any fluff. It is appropriately sized for a simple tool, front-loaded, and every word 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?

The tool is simple with one parameter and clear annotations, so the description plus schema cover the basics. However, the openWorldHint and destructive nature could benefit from additional context about side effects or constraints, which is absent. It is adequate but leaves some gaps.

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 input schema contains a description for the 'id' parameter ('id of Bill to delete'), giving 100% schema description coverage. The description adds nothing beyond this, so a baseline score of 3 is appropriate since the schema does the heavy lifting.

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 Bill' clearly states the verb 'Delete' and the resource 'Bill', which is specific enough to understand the tool's function. It distinguishes from sibling tools by naming the resource type, though it does not add any additional nuance beyond the tool name itself.

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 such as cancel_invoice or delete_purchase_order. No context, prerequisites, or exclusions are provided, leaving the agent to infer usage only from the resource name.

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