connect_widgets

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Draw a connected arrow' without explaining whether this is a create operation, what side effects it has, how coordinates are interpreted, or what happens if the widgets don't exist. Terse to the point of lacking transparency.

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, front-loaded sentence that efficiently states the purpose and core inputs. However, for a tool with 11 parameters and complex geometry, it is notably under-specified. It is concise but not appropriately sized given the tool's complexity.

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 11 parameters and no output schema, the description should provide information about return values, error behavior, and how the arrow geometry is computed. It provides none of this, making it incomplete for a tool of this complexity.

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 only 27%, and the description adds minimal value. 'Provide source/target IDs and positions' hints at some parameters but leaves sourceWidth/sourceHeight and X/Y coordinate semantics unexplained. It also omits any mention of the style or arrowType options, which are available 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's function: drawing a connected arrow between two widgets. This specific verb+resource distinguishes it from sibling tools like connect_widgets_batch, which handles batch connections, and create_arrow, which likely creates a generic arrow.

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 usage guidance is provided. The description does not mention when to use this tool versus connect_widgets_batch or create_arrow, nor does it specify any prerequisites or context for choosing this tool over alternatives.

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