delete_tree

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

With no annotations provided, the description must disclose behavioral traits. It only states the action ('Delete a tree') without explaining consequences (e.g., cascade deletion, reversibility, permission requirements). This is insufficient for an agent to understand side effects.

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 very concise (three words) with no wasted text. However, it is too brief to be fully informative; a longer description could add value without becoming verbose.

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?

Given the tool has one parameter, no output schema, and sibling tools that also modify trees (e.g., 'prune_tree', 'clear_all_trees'), the description does not provide enough context for an agent to understand the tool's scope, effects, or relationship to alternatives.

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% (the single required parameter 'id' has a schema description 'Tree ID'). The description adds no additional meaning beyond what the schema already provides, so it meets the baseline but does not enrich parameter understanding.

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 tree' clearly states the verb (delete) and the resource (a tree), making the primary action unambiguous. However, it does not differentiate from sibling tools like 'prune_tree' or 'clear_all_trees', which might have similar effects, so it lacks some specificity.

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 on when to use this tool versus alternatives like 'prune_tree' or 'clear_all_trees'. The description does not mention prerequisites, allowed contexts, or when deletion is inappropriate.

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