sch_create_netflag

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

No annotations provided, and the description carries full burden. It does not disclose whether creating a flag is destructive (e.g., replaces existing flags), what happens if parameters are invalid, or side effects on the schematic.

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?

Single sentence with no unnecessary words. Efficiently conveys core purpose, though additional details could be added without harming conciseness.

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 6 parameters, no output schema, and no annotations, the description is insufficient. Lacks details on return value, error conditions, and post-creation behavior.

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 low (17%). The description adds meaning for 'net' and 'position' (implicit from 'attached to a net at a position'), but does not explain parameters like 'mirror' and 'rotation' beyond what the schema provides.

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 ('Create'), the resource ('net flag'), provides an example ('e.g. VCC/GND short symbol'), and specifies attachment to a net at a position. It distinguishes from sibling tools (e.g., sch_create_wire, sch_place_component) by targeting a specific schematic element.

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 guidance on when to use this tool versus alternatives. The description does not mention prerequisities (e.g., net must exist), exclusions, or related tools for creating other elements.

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