Add schematic circle

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

Annotations already indicate this is a non-read-only, non-idempotent write operation. The description adds that fillColor 'none' leaves the circle unfilled, which is a useful behavioral detail but does not cover other traits (e.g., side effects, coordinate system, or permission requirements). No contradiction with annotations.

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 two sentences long, front-loads the core action and purpose, and the second sentence adds targeted guidance on fillColor. No fluff or redundant information.

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 9 parameters and low schema coverage, the description omits critical context such as coordinate units, line type interpretation, constraints on radius, and the fact that confirmWrite must be a literal boolean true. The presence of an output schema does not compensate for missing usage context.

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 only 22% schema coverage, the description should compensate by explaining parameter meanings. It only addresses fillColor, clarifying that 'none' means unfilled. Other parameters (centerX, centerY, radius, confirmWrite, etc.) are left unexplained, leaving agents to rely on parameter names, which may be insufficient.

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 ('Draw a circle'), the target location ('on the schematic sheet'), and the purpose ('decorative marker or custom symbol element'). It distinguishes from electrically meaningful siblings by emphasizing that it is cosmetic only with no electrical meaning.

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 implies the tool is for decorative purposes only ('Cosmetic only, no electrical meaning'), but it does not explicitly state when not to use it or provide alternative tools for electrically significant shapes or other decorative primitives like rectangles or polygons.

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