sd_delete_nodes

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds behavioral context: deletion is gated by confirm, and it operates on a single graph. This goes beyond the annotation but does not detail side effects like cascading deletion of edges.

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 concise sentence, front-loaded with the action and key constraint. No redundant or filler content.

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 tool, the description is minimal. It does not cover what happens if confirm=false, how errors are reported, or the impact on related nodes/edges. However, the output schema and annotations provide some structural and safety context, so it is borderline adequate.

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 compensate. It links 'confirm true' to the confirm parameter and 'explicit nodes' to node_identifiers, but doesn't explain the format of identifiers or the GraphRef structure. Some semantic value is added, but gaps remain.

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 states the tool deletes explicit nodes from one graph, with a specific condition (confirm=true). This distinguishes it from siblings like create or move tools, and the phrase 'explicit nodes' clarifies that only listed nodes are affected.

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 condition 'only when confirm is true' gives clear context for when the deletion actually occurs, implying the tool is safe to call with confirm=false for validation. However, it does not mention alternatives or explicitly state when not to use it.

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