set_data_color

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

No annotations are provided, so the description carries the full burden. It clarifies what 'data colour' means (default series fill) but does not disclose side effects such as overwriting existing fills, whether changes are reversible, or if specific permissions or visual types are required. The mention of 'default series fill' adds some semantic value, but behavioral transparency is minimal.

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 two sentences with no wasted words. It leads with the primary action, adds a clarifying parenthetical, and finishes with a practical usage tip. Every part contributes value, making it well-structured and appropriately sized.

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 the tool has four required parameters, no output schema, and no annotations, the description is too sparse for full completeness. It explains what 'data colour' means but omits how to identify the visual (pageName/visualName), any prerequisites, expected effects, or return values. The description is not completely inadequate for a simple setter, but it leaves significant 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 only 25% (only 'color' has a description). The description adds meaning for 'color' by explaining it as the default series fill and suggesting theme color usage, but it does nothing for reportSessionId, pageName, or visualName. These remain undocumented, and the description does not compensate for the missing parameter semantics.

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 a specific verb and resource: 'Set a chart's data colour (the default series fill).' This explicitly distinguishes it from related sibling tools like set_theme_data_colors by clarifying that this targets the chart's data series fill, not theme-level colors. The parenthetical clarification adds precision.

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 a clear usage context: 'For a branded single-measure chart, point this at a theme colour.' This gives a concrete scenario and implies a recommendation, though it does not explicitly mention alternatives or when not to use the tool. It earns a 4 for giving relevant context without exclusions.

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