wacta_delete_cta

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

No annotations are provided, so the description carries the full burden. It only states that the tool deletes a CTA, but does not disclose whether the deletion is permanent, whether it cascades to related data, or any other side effects. For a destructive operation, this lacks essential behavioral detail.

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 a single, front-loaded sentence with zero fluff. It states exactly what the tool does and the input parameter in an efficient manner.

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?

The tool is simple (one parameter, no output schema), so the description could be complete with the basic action. However, it lacks any mention of return values, error behavior, or permanence of deletion, which are relevant for a delete operation. The description is adequate but leaves important gaps for a fully informed agent.

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 schema only defines 'slug' as a string with no description (coverage 0%). The description's 'por su slug' explicitly indicates that the slug parameter is the identifier used for deletion, adding meaning beyond the raw schema. For a single simple parameter, this is sufficient for correct invocation.

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 the action ('Elimina' = deletes) and the resource ('CTA del Registro Único') with the method ('por su slug'). It distinguishes itself from sibling tools like wacta_save_cta (create/update) and wacta_list_ctas (list).

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?

Usage is implied by the tool name and description: use when deleting a CTA by slug. However, there is no explicit guidance about when not to use it, prerequisites, or alternatives. The context is clear from the sibling tools but not explicitly stated.

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