apply_gradient_rect

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

With no annotations, the description must disclose behavioral traits. The single sentence does not reveal side effects, such as whether the gradient overwrites existing pixels, how the rectangle is created (if missing), or any limits (e.g., alpha, color format). This is insufficient for a mutation tool.

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 very concise (one sentence, front-loaded). It earns its place by being clear, but it sacrifices important detail. A longer description would improve completeness without being overly verbose.

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 11 parameters (9 required), no output schema, and no annotations, the description is grossly incomplete. It fails to explain essential aspects like color format, gradient direction, behavior when layer exists or not, and return value. The tool is complex, and the description leaves major gaps.

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% (only titles), so the description must add meaning. It does not explain parameters like color_start/color_end (format?), horizontal (orientation?), create_if_missing, or the coordinate system. The description adds no semantic value beyond the schema.

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 specifies the action 'Apply', the object 'linear gradient fill', and the target 'rectangle'. It clearly distinguishes from sibling tools like draw_rectangle (which likely draws outlines) and fill_area (solid fill).

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 versus alternatives. It does not mention scenarios, prerequisites, or exclusions, leaving the agent without context for selection.

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