delete_product

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

destructiveHint=true already tells the agent this is a destructive mutation, so the safety profile is covered by structured data. The description adds nothing beyond that: no statement about irreversibility, whether the deletion is soft (cf. list_deleted_documents/recover_document) or hard, or what happens to references. For a deletion tool this is a real gap.

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 operation front-loaded and zero filler. It is efficient, though its brevity comes at the cost of under-specification rather than being genuinely complete.

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 destructive, id-required mutation with no output schema and an undocumented required parameter, the definition says far too little. It should at minimum cover reversibility/soft-delete behavior and confirm what the id refers to.

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 coverage is only 50%: company_id is documented in the schema, but the required 'id' has no description at all. The description adds no meaning about what the id identifies or whether company_id scoping affects the deletion, so it fails to compensate for the coverage gap.

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 names a specific verb and resource ('Elimina un prodotto o servizio a listino'), so an agent immediately knows this removes a catalog product/service. It does not, however, distinguish itself from the many sibling delete_* tools (delete_supplier, delete_vat_type, delete_client), relying on the name alone for that routing.

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 versus update_product (e.g., deactivate/hide instead of delete) or list_products/get_product for finding the id first. No prerequisites, no mention of consequences for products already referenced on issued documents.

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