delete_tree

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

With no annotations provided, the description carries the full burden of explaining behavioral side effects. It states that a tree is deleted but does not disclose whether deletion cascades to children, whether it is irreversible, what permissions are required, or what the response indicates. This leaves the agent without insight into destructive consequences.

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 sentence with no filler. The action and target are front-loaded and every word contributes to meaning, making it optimally concise for such a simple tool.

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 tool with no output schema and no annotations, the description is minimally adequate. It tells the agent what input is needed and what effect occurs. However, it does not explain the return value or any cascading side effects, which would be valuable for a destructive operation.

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 input schema already describes treeId as 'The ID of the tree to delete' with 100% coverage. The description does not add further semantic detail, so it stays at the baseline for fully documented schemas.

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 identifies the action ('Delete'), the resource ('a tree'), and the identifying input ('by ID'). It is distinguishable from broader operations like delete_session_trees or clear_tree, though it does not explicitly contrast itself with those siblings.

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 phrase 'Delete a tree by ID' implies the tool should be used when a specific treeId is known and that single tree must be removed. However, it provides no explicit guidance about when not to use this tool or where alternatives like delete_session_trees would be more appropriate.

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