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

Annotations already flag destructive=true, idempotent=false, and openWorld=true. The description adds useful authorization and ownership context: only nodes created by the same agent key or account can be removed, and key or sign-in is required.

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?

Two short clauses, front-loaded with the action and resource, then the ownership/auth constraint. No wasted text.

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 mutation, it provides ownership and authentication context, and annotations cover the safety profile. However, it remains ambiguous about what 'take down' means operationally, whether data is recoverable, and how the required id should be formed.

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 0%, so the description must carry parameter meaning. It clarifies that id refers to one of the caller's own nodes and that key is used for authentication or sign-in, but it does not describe id format or further distinguish the optional key.

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?

States a specific action and resource: taking down one of the caller's own Trana nodes. The ownership constraint helps distinguish it from node_create, node_edit, and other node operations, though it does not explicitly name alternatives.

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?

Conveys the prerequisite that the node must belong to the caller and that key or sign-in is needed. It does not explain when to choose removal versus node_edit/status or mention any exclusions, so usage is implied rather than fully guided.

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