draw_line_at

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

With no annotations, the description carries full burden but only says 'draw a line'. It does not disclose any side effects, coordinate system, behavior if layer/frame missing (despite a create_if_missing parameter), or whether it overwrites existing lines. The description is insufficient for an agent to anticipate tool behavior.

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 short sentence that directly states the core purpose. It is front-loaded and contains no filler. Every word earns its place, though it could be expanded without losing conciseness.

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 tool has 10 parameters, 7 required, and no output schema or annotations. The description is minimal and does not explain return values, coordinate system, interaction with existing content, or error conditions. Given the tool's complexity, the description is incomplete.

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 the description must compensate but doesn't describe any parameters. While parameter names like x1,y1,x2,y2 are intuitive, the description adds no context about formats (e.g., color hex format, thickness units, create_if_missing implications). The agent relies solely on schema titles and defaults.

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 line) and the target context (specific layer/frame). This distinguishes it from similar sibling tools like 'draw_line' (which likely uses current layer/frame) and other draw-at tools.

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 provides no guidance on when to use this tool over alternatives, nor any prerequisites or conditions. Siblings like 'draw_line' are not mentioned, and there is no hint about when to choose this tool vs others.

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