Delete Workspace Subgraph

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

Annotations already mark destructive; description adds 'member nodes are NOT deleted' and explains name resolution process, providing critical beyond-annotation context.

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?

Concise, front-loaded with action and outcome. Arg list is well-organized. No superfluous sentences.

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?

With output schema present, description adequately covers behavior, parameter resolution, and return type. No gaps for the tool's complexity.

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 covers all parameters; description adds resolution logic for subgraphName and preferred status for subgraphID, enhancing utility beyond schema.

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?

Description clearly states the action (delete a subgraph) and distinguishes from siblings by specifying what is affected (nodes not deleted). Verb+resource structure is explicit.

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?

Describes when to use subgraphID vs subgraphName with repoPath, and mentions confirmation requirement. Lacks explicit when-not-to-use but infers well from destructive nature.

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