extract_report_colors

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

Despite no annotations, the description proactively declares 'READ-ONLY', mitigating side-effect concerns. It also details the output scope (color literals, locations, theme paths), adding behavioral context beyond the schema. Missing session prerequisite or error behavior, but sufficient for a read-only 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?

A single, dense sentence that front-loads the critical 'READ-ONLY' flag and uses concise terminology. No filler or redundant phrasing.

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?

For a single-parameter, read-only tool, the description covers the essential output details (color inventory, locations) and workflow context. It does not explain the parameter or error cases, but the simplicity of the tool reduces the need for extensive elaboration.

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 schema has one parameter (reportSessionId) with 0% description coverage. The description does not explain this parameter or how it relates to the tool's function. With low schema coverage, the description should compensate, but it provides no parameter guidance.

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 explicitly states it inventory all hardcoded colour literals across visuals and theme, with exact locations, making the verb and resource clear. It also distinguishes from siblings by positioning itself as the 'scouting pass before recolor_report'.

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?

Clearly places the tool in a workflow ('The scouting pass before recolor_report'), implying when to use it. It does not explicitly name alternatives or exclusion scenarios, but the context is strong enough to guide selection.

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