disconnect_shader_nodes

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It fails to mention potential side effects, such as whether disconnecting all links affects other connected nodes, or if the operation is reversible. It only states the action and the return type, missing critical safety information.

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 concise and front-loaded with the main purpose. The args list follows the schema structure, making it easy to parse. However, the args section is somewhat redundant and could be integrated more elegantly.

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 simple tool with four parameters and an output schema ('Returns confirmation dict'), the description provides enough context to understand the operation and return value. It covers the essential aspects without being overly verbose.

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?

With 0% schema description coverage, the description must compensate. It lists parameter names and basic meaning (e.g., 'Name of the material') but adds no format constraints, allowed values, or behavioral context. This adds minimal value over the schema structure itself.

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 action: 'Disconnect all links from a specific socket on a shader node.' It uses a specific verb ('Disconnect'), a resource ('shader node'), and a specific part ('socket'). This distinguishes it from related tools like connect_shader_nodes.

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 explicit guidance is provided on when to use this tool versus alternatives. The purpose implies it should be used when you need to disconnect all links from a socket, but there is no mention of prerequisites, scenarios, or when not to use it. This is a minor gap given the simplicity of the operation.

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