draw_curve

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

No annotations provided, so description carries full burden. It lacks behavioral details like whether it modifies existing pixels, what 'steps' concretely does beyond 'controls smoothness', or if it returns any output.

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?

Two sentences, directly states purpose and key parameter (steps) with no extraneous words; front-loaded with 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?

Given no output schema, no annotations, and many sibling drawing tools, the description leaves gaps: how curve interacts with existing art, typical step values, whether color uses a parameter (mentioned in schema but not description).

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 0%, so description must compensate. It explains geometric parameters (x0,y0, control point, x1,y1) and 'steps', but omits filename, color, frame, layer—important context for an agent.

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?

Description clearly specifies the action (draw a quadratic Bézier curve), the geometric elements (start point, end point, control point), and distinguishes from sibling drawing tools by naming the curve type.

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?

Implies usage for smooth curved lines, but no explicit guidance on when to choose this over alternatives like draw_line or draw_ellipse; no when-not-to-use conditions.

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