tochka_delete_invoice

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

The annotations include 'destructiveHint: true', which already signals destruction. The description's 'Delete' adds no further behavioral details such as irreversibility, authorization needs, or side effects. With annotations present, the description does not enhance transparency beyond the verb.

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 concise with only two sentences, front-loading the purpose and parameter hint. No extraneous words; every sentence adds value.

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 simple delete tool with one parameter, the description covers purpose and parameter origin. Annotations cover destructiveness, and an output schema exists (though not shown). No critical gaps; a user might want a note on what happens after deletion (e.g., whether it's soft or hard), but the annotations mitigate this.

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 description explains that 'document_id' is an 'Invoice UUID from tochka_invoice result', which adds meaningful context beyond the schema's simple type string. This helps the agent understand the source and format of the required parameter.

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 'Delete an invoice by document ID' which specifies the verb (delete) and resource (invoice) with a specific identifier. It distinguishes from sibling tools like 'tochka_delete_closing_document' by targeting invoices.

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?

No guidance is provided on when to delete an invoice versus alternatives like 'tochka_untrack_invoice' or 'tochka_send_invoice_email'. The description lacks context for selecting this tool over others.

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