Ase Draw Contour

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic drawing action and does not explain that it modifies the sprite at sprite_path, what coordinate space points use, how 'closed' and 'thickness' affect the result, or which frame/layer are affected.

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 extremely concise and front-loaded, with no filler or redundancy. However, it is so brief that it skips structural details that would help an agent, so it earns high marks for conciseness but not full marks for structure.

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 seven parameters, no annotations, and a mutation-oriented drawing operation, a single clause is insufficient. Critical information such as the point object format, coordinate system, default frame/layer behavior, and the meaning of closed/thickness is missing, making the tool hard to invoke correctly in practice.

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 description coverage is 0%, so the description must compensate, but it only loosely associates 'points' with the path. It does not clarify the structure of a point object, nor does it add meaning for sprite_path, color, frame, layer, closed, or thickness.

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 uses a specific verb ('Draw') and a distinct resource ('polyline/polygon') rather than just restating the tool name. The phrase 'through points' helps differentiate it from single-segment draw_line, draw_rectangle, and draw_circle siblings, although it does not explicitly name any sibling.

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 gives no explicit when-to-use guidance, no exclusions, and no mention of alternatives. An agent must infer from the name and the word 'polyline/polygon' that this is for connected multi-point paths, but that inference is not made explicit.

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