siigo_delete_product

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. 'Delete a product' implies a destructive mutation, but the description doesn't disclose whether deletion is permanent or reversible, what permissions are required, whether there are rate limits, what happens to associated data, or what the response looks like. For a destructive operation with zero annotation coverage, this is dangerously inadequate.

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 maximally concise at just three words. While this represents severe under-specification in terms of content, from a structural perspective it's perfectly front-loaded with zero wasted words. Every word ('Delete', 'a', 'product') contributes directly to the core purpose statement.

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 mutation tool with no annotations and no output schema, the description is completely inadequate. It doesn't explain what constitutes successful deletion, what errors might occur, what permissions are needed, or any behavioral nuances. The agent cannot safely or effectively use this tool based on the provided description alone.

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 has 100% description coverage (the 'id' parameter is fully documented as 'Product ID'), and there's only one parameter. The description adds no parameter information beyond what the schema provides, but with complete schema coverage and minimal parameters, the baseline is appropriately high. The description doesn't need to compensate for any gaps.

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 'Delete a product' is a tautology that merely restates the tool name 'siigo_delete_product'. While it identifies the action (delete) and resource (product), it provides no additional specificity about what constitutes a product in this context or how deletion works. It doesn't distinguish this tool from sibling deletion tools like 'siigo_delete_invoice' or 'siigo_delete_purchase' beyond the resource name.

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 provides absolutely no guidance about when to use this tool versus alternatives. There's no mention of prerequisites (e.g., product must exist), consequences, or when to choose this over other product-related tools like 'siigo_update_product' or 'siigo_get_product'. The agent receives zero contextual direction about appropriate usage scenarios.

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