Disconnect Attributes

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

Annotations indicate idempotence and non-destructiveness, which align with the tool's purpose. The description adds the three-mode behavioral detail, but does not disclose potential side effects (e.g., attribute values resetting to default).

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, clear sentence that front-loads the core purpose and efficiently conveys the three usage scenarios with no unnecessary words.

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 tool with three modes and an output schema, the description adequately covers the basic functionality. However, it could be more complete by mentioning that the source and destination are plug attributes, and noting that disconnected values revert to defaults.

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?

Input schema has 100% coverage with descriptions for both parameters. The description adds semantic value by explaining how the combination of source and destination determines the disconnection behavior (specific, all outgoing, all incoming).

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), the resource (attributes in Maya), and distinguishes three usage modes (specific connection, all outgoing, all incoming). It effectively differentiates from sibling tools like connections.connect and connections.list.

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 description implies usage by describing three modes, but does not explicitly state when to use this tool vs alternatives (e.g., connections.list, connections.get). No guidance on prerequisites or when not to use is provided.

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