apply_color

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

The description gives no behavioral details beyond the action itself. No annotations exist to compensate. It does not disclose side effects (e.g., mutates object), required permissions, or error conditions (e.g., missing swatch). 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 a single sentence, which is concise, but it sacrifices essential information. It achieves brevity at the cost of clarity and completeness, making it barely adequate.

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 4 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain how to use the parameters, what the output is, or any constraints. An agent would struggle to invoke this tool correctly without additional context.

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?

The description adds no meaning beyond the input schema. Schema description coverage is 75% (3 of 4 parameters have descriptions), but the description does not explain how property (fill/stroke) works or that pageIndex defaults to 0. It fails to compensate for the missing description of the 'property' parameter.

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 'Apply color to an object' is a generic verb+resource, but it lacks specificity about what kind of color (fill/stroke) and what type of object. It does not distinguish from sibling tools like apply_paragraph_style or create_color_swatch, though no direct competitor exists. The purpose is clear but too vague for precise selection.

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?

No guidance is provided on when to use this tool versus alternatives such as list_color_swatches or create_color_swatch. There is no mention of prerequisites (e.g., the object and swatch must exist) or context like whether it's for fill or stroke.

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