no_connect_pin

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

The description reveals the behavior ('Resolves pin position and places a no-connect flag') beyond the annotations. It indicates a mutation (readOnlyHint=false) without contradiction. However, it lacks details on side effects or permissions.

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, but the first two sentences are slightly redundant. The inclusion of an args list is helpful.

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 3 parameters and an output schema, the description covers the core functionality and parameter meanings adequately. It does not explain the output schema, but that is not required.

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 adds essential meaning by explaining each parameter: reference (e.g., 'U2'), pin_name (e.g., 'NC' or '3'), and schematic_path. This compensates for the bare 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 action ('Place a no-connect flag') and the resource ('on a component pin'), distinguishing it from siblings like 'connect_pins' and 'list_schematic_no_connects'.

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 does not explicitly state when to use this tool versus alternatives. While the purpose is clear, there is no guidance on when a no-connect flag is appropriate or how it differs from simply leaving a pin unconnected.

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