wafeq_bills_destroy

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

Annotations already declare destructiveHint=true, and the description adds the meaningful context that the record is 'permanently removed.' It also labels the operation as destructive up front, reinforcing the irreversible nature beyond what the annotation alone conveys.

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 repeats 'Delete bill' or its equivalent multiple times: 'DESTRUCTIVE · deletes · Bills,' the title, and 'Endpoint for deleting an existing bill.' It is short but redundant; a single concise sentence would be more effective.

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 essential facts are present: the action is destructive, permanent, and targets a specific bill, with idempotency protection covered in the schema. However, it does not explain whether deletion is allowed in all bill states, what happens to associated line items, or when not to use this operation, leaving moderate 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 documents idempotency_key well, but the required 'id' parameter has no description. The tool description adds no parameter-specific meaning, so 50% of the parameters remain semantically under-specified and the agent must infer that 'id' is the bill identifier from the endpoint path.

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 the operation: deleting a bill via DELETE /bills/{id}/, and explicitly notes that the record is permanently removed. This distinguishes it from sibling retrieve, update, and partial_update operations.

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 implies usage by saying it deletes a bill, but it offers no guidance on when to choose this tool versus alternatives, no prerequisites, and no warnings about deleted bills with related data. An agent must infer the appropriate usage context.

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