treeflow_delete_leaf

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. It states the destructive action but does not mention reversibility, cascading effects, permissions, or what happens after the deletion, which is important context for a delete operation.

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 communicates the action and the object with no redundant filler. The parenthetical clarification 'leaf' is compact and valuable.

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 one-parameter leaf-delete operation, the purpose and parameter are sufficiently covered for basic invocation. However, with no annotations and no output schema, the description does not disclose the operation's effects or return behavior, so it is only minimally complete.

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 already covers 100% of the single parameter with a description ('ID del nodo a eliminar'), and the tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate given full schema coverage.

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 uses a specific action verb ('Elimina') and a clear resource ('nodo (leaf) del canvas'), making the tool's function unmistakable. The parenthetical '(leaf)' also helps distinguish it from sibling deletion tools like treeflow_delete_branch.

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 tool type and the word 'leaf' imply when it should be used, and the delete operation is self-explanatory once a leaf_id is available. However, there is no explicit guidance about when not to use it or how it differs from deleting a branch, intent, or other resource.

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