draw_line_at

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

No annotations provided. Description does not disclose any behavioral traits beyond basic purpose. Does not mention effects (additive vs overwrite), undo implications, coordinate system, or the create_if_missing parameter behavior. Minimal transparency.

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, 9 words, no redundancy. Very concise, but at the expense of completeness. Front-loading is fine, but too short for a tool with 10 parameters.

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?

Despite having 10 parameters, 7 required, no output schema, and no annotations, the description only gives a minimal purpose. It fails to explain return values, side effects, coordinate system, or how the line is rendered. Inadequate for an agent to use correctly.

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%. The description adds no meaning beyond parameter names. Parameters like x1, y1, etc. are not explained in terms of coordinate system, range, or relation to canvas. Defaults are in schema but not contextualized.

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 states it draws a line on a specific layer/frame, which is a specific verb-resource pair. It distinguishes from sibling draw_line by explicitly mentioning layer and frame, but does not explicitly differentiate from draw_line_at itself (though that is the same tool). Still clear enough.

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: when you want to draw a line on a specific layer/frame. No when-not or alternatives mentioned. Siblings like draw_line exist but no guidance on choosing between them.

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