td_disconnect

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

The description simply restates the action without disclosing behavioral details beyond what annotations already provide. Annotations indicate destructiveHint=true, and the description adds no context about side effects, reversibility, or error behavior.

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 one concise sentence that front-loads the action. Every word is essential with no filler.

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?

Despite having an output schema, the description lacks context for a destructive tool. It does not clarify edge cases (e.g., invalid index, missing node), prerequisites, or what happens to connections after disconnection.

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 100%, so baseline is 3. The description adds no additional meaning to parameters beyond their schema definitions. The schema already explains path, index, and connector_type adequately.

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's action: disconnecting a node's input or output connector. It uses a specific verb (disconnect) and resource (node's connector), which distinguishes it from sibling tools like td_connect_nodes or td_delete_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?

No guidance is provided on when to use this tool vs alternatives, such as when to disconnect vs delete a node or connection. The description does not mention prerequisites or 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.