kicad.add_global_label

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

With no annotations provided, the description carries the full burden. It discloses the connectivity scope (cross-hierarchical) but fails to mention side effects, idempotency, coordinate units, or what the output schema contains. The mention of hierarchical connectivity provides minimal behavioral context.

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 single-sentence structure is front-loaded with the action verb and contains zero waste. Every word earns its place, though given the 0% schema coverage and lack of annotations, the description is arguably too concise and lacks necessary expansion.

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?

Despite having an output schema (reducing the need to describe return values), the description is inadequate for a 5-parameter CAD tool with zero schema documentation. It omits coordinate system details, valid enum values for 'shape', and placement behavior—information essential for correct invocation.

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 completely fails to compensate. It does not explain coordinate units (x, y), angle units, valid shape values (only the default 'bidirectional' appears in schema), or naming conventions for the label—critical omissions for a CAD placement tool.

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 provides a specific verb ('Add') and resource ('global label'), and crucially distinguishes this tool from sibling kicad.add_net_label by specifying it 'connects across hierarchical sheets'—a critical distinction in EDA tools between local and global nets.

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 parenthetical '(connects across hierarchical sheets)' implies when to use this tool (for cross-sheet connectivity), but it does not explicitly state when NOT to use it, name alternatives like add_net_label for local connections, or mention prerequisites.

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