Create Connections

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

The description discloses three behavioral modes (create, set default, check default) and hints at non-destructive behavior. However, it does not elaborate on side effects or permissions, and the openWorldHint annotation suggests potential undiscovered side effects.

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 concise with two sentences, front-loading the main purpose and usage conditions. 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?

Given the presence of an output schema, the description adequately covers the three operational modes. It does not specify what happens if both parameters are passed (likely invalid) or prerequisites like node existence, but these are reasonable gaps for a clear tool.

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 parameters are well-documented. The description adds value by explaining the conditional logic (mutually exclusive usage) and the check-default behavior when no parameters are given, which is not in the 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?

The description clearly states the tool creates connector lines, sets/checks the default connector template. The verb 'Create' is used but the tool has multiple functions, which is still clear. It distinguishes from sibling tools as none seem to handle connections.

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 explicitly says when to pass each parameter: 'Pass connectorId to set a default, connections to draw lines, or nothing to check the current default.' This provides clear situational guidance, though it does not discuss when not to use the tool or alternatives.

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