treeflow_delete_message_template

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only restates the destructive action ('Elimina') without adding context about irreversibility, side effects on associated resources, or error cases. It adds no behavioral detail beyond what the tool name already implies.

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 short, clear sentence that immediately conveys the operation. It is efficiently front-loaded and contains no unnecessary words or repetition, making it easy to parse.

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 operation with no annotations and no output schema, this description is too sparse. It does not mention consequences, success/failure indicators, dependencies, or any usage context, leaving the agent without enough information to invoke it confidently in a real scenario.

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 description coverage is 100% and the template_id parameter is already described as 'ID de la plantilla a eliminar'. The description does not add any additional parameter semantics, but the schema fully covers it, so the baseline 3 is appropriate.

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 'Elimina una plantilla de mensaje' uses a specific verb (eliminar) and resource (plantilla de mensaje), clearly stating the operation. It distinguishes from sibling tools like list/create/update message templates by the destructive verb, so an agent can identify its purpose without opening the schema.

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 about when to use this tool or when to prefer an alternative. The description simply states the action, with no prerequisites, no mention of idempotency, no warnings about when deletion is appropriate. Nothing is provided to help choose between this and related template tools.

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