sd_disconnect_nodes

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

Annotations provide limited safety info (all false). The description adds context that the tool handles only 'one explicit existing' connection, which is useful behavioral information. It does not disclose side effects such as whether the operation is reversible or what happens if the connection does not exist.

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 extremely under-specified for a tool with 5 required parameters. It is concise but not appropriately sized; it omits necessary context and reads more like a title than a useful description.

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 5 parameters, 0% schema coverage, and no guidance on side effects or return values (despite an output schema), the description is incomplete. It does not explain what 'explicit' means, prerequisites, or the operation's outcome, leaving significant gaps for an agent to invoke it correctly.

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%, and the description does not explain the parameters. While parameter names like source_node, source_property, target_node, target_property are fairly self-explanatory, the description adds no additional meaning about how they relate or any requirements, so it fails to compensate for the lack of schema descriptions.

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 a specific action ('Disconnect') on a specific resource ('one explicit existing property connection'). It distinguishes from siblings like sd_connect_nodes and sd_delete_nodes by focusing specifically on disconnecting an existing connection.

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 phrase 'explicit existing property connection' implies the tool is intended for disconnecting connections that already exist and are explicit, providing an implied usage context. However, it does not explicitly mention when to use it over alternatives or any exclusions.

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