delete_node

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

Discloses key behaviors: soft-delete (not permanent), cascading default, recoverability. No annotations provided, so description carries burden. Could mention authorization or side effects, but covers core traits.

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?

Three efficient sentences, each adding value. Front-loaded with primary action. No redundant 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?

Covers core purpose and recovery, but lacks description of return value and does not fully document all parameters. With low schema coverage and no output schema, description could be more thorough.

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 25% (only plan_id described). Description adds context for cascade_children and implies node_id, but does not explain reason parameter. Partial compensation for low 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?

Clearly states 'soft-delete a node', specifying the verb and resource. Distinguishes from siblings like delete_plan (deletes plan) and update_node (updates node).

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?

Provides explicit context: cascades to children by default and is recoverable. Gives recovery method via update_task. Doesn't state when not to use but offers enough guidance for an agent.

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