fiken_delete_sale

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds no additional behavioral context (e.g., irreversibility, permission requirements). With annotations present, the description's lack of extra detail results in a neutral score.

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 extremely concise (3 words), which is efficient for a simple delete operation. However, it lacks any structured information about parameters, outcomes, or usage context, making it barely adequate.

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?

Given the tool's simplicity (1 parameter, no output schema), the description fails to provide expected context such as return values, success/failure behavior, or side effects. More information (e.g., 'This action cannot be undone') would improve completeness.

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 sole parameter 'saleId' has no description in the schema (0% coverage), and the tool description does not explain its meaning or format. While its purpose might be inferred from context, the description adds no value beyond the schema structure.

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 'Deletes a sale' clearly identifies the action and resource. While brief, it effectively communicates the core function. It distinguishes from similar tools like 'fiken_delete_sale_draft' by specifying 'sale' rather than 'sale draft'.

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 'fiken_delete_sale_draft' or 'fiken_get_sale'. No prerequisites or exclusion criteria are provided.

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