sketch_centerline

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

The description does not disclose any behavioral traits beyond the obvious action. With no annotations, it fails to mention side effects (e.g., modifying the active sketch), ownership of the created entity, or any dependencies (e.g., an active sketch must be open).

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 sentence with no unnecessary words. It is efficient and immediately conveys the core action.

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?

The description lacks context about what a centerline is (construction vs. regular line), whether the tool requires an active sketch, and what the return value is. Given no output schema and no annotations, the description should provide more behavioral and 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?

The input schema provides descriptions for start and end coordinates (e.g., 'Start X coordinate in mm'), so schema coverage is high. The description adds no additional semantic information, so the baseline score of 3 is appropriate.

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 verb 'Draw' and the resource 'centerline in the active sketch'. It is specific and distinguishes from sibling tools like sketch_line, which draws a regular line. However, it does not clarify that a centerline is typically a construction line used for symmetry, which could improve clarity.

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 is provided on when to use this tool versus alternatives like sketch_line or sketch_circle. The description gives no context about prerequisites (e.g., an active sketch must exist) or typical use cases (e.g., drawing symmetry axes).

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