delete_numbering_serie

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

With no annotations at all, the description carries the full behavioral burden and largely defaults to it. It does not state that the operation is irreversible, whether deletion fails when documents reference the series, what error shape to expect, or what permissions are required. The 'Holded API v2' suffix is citation, not behavioral context.

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 front-loaded sentence with the verb first and no filler; it is easy to parse. The parenthetical API version adds little, but nothing is padded or buried.

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 two-parameter mutation with no annotations and no output schema, the description should say more about consequences and failure modes. An agent knows what it deletes but not what it risks or what it will get back.

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 100% and both parameters are documented in the schema, including an 11-value enum for docType, so the baseline of 3 applies. The description adds no meaning beyond the schema — it does not explain why the document type must accompany the serie id or how the pair is scoped.

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?

Specific verb (Delete) plus specific resource (numbering serie), and the (Holded API v2) tag scopes the API generation. It is clearly distinguishable from get/create/update_numbering_serie siblings by the verb alone, but the description never names or contrasts those alternatives.

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 when-to-use, when-not-to-use, or prerequisite guidance. There is no warning about deleting a series that may be assigned to documents, and no pointer to the safer siblings (get_numbering_series, update_numbering_serie) for callers who only want to inspect or modify.

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