freeagent_delete_bill

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

Annotations already state destructiveHint=true and readOnlyHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that: it does not say the deletion is permanent or irreversible, whether attachments or linked transactions are affected, what permissions are required, or what happens if the bill ID does not exist.

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?

A single short sentence with the verb and resource front-loaded and zero filler. Nothing is redundant or padded.

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 one-parameter mutation with annotations covering the safety profile and no output schema, the definition is minimally sufficient to invoke the tool correctly. However, given it is destructive, an agent would benefit from knowing about irreversibility and error behavior, which are absent.

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 100% and the single bill_id parameter is fully documented in the schema, so the baseline is 3. The description contributes no additional meaning such as accepted ID formats or where to obtain a valid bill_id (e.g., from freeagent_list_bills).

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 gives a specific verb and resource ("Delete a bill") with the target service named, so an agent knows exactly what operation is performed. It does not distinguish itself from siblings such as freeagent_get_bill, freeagent_update_bill, or freeagent_delete_invoice, so it falls short of a 5.

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 when-to-use guidance, no mention of preconditions (e.g., whether the bill must be in a deletable state), and no reference to alternative tools like freeagent_update_bill if the intent is correction rather than removal. Usage must be inferred entirely from the tool name.

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