util_color_by_element

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

There are no annotations, so the description must carry the behavioral disclosure burden. It states the coloring action but does not mention that existing colors are overwritten, whether the optional selection restricts scope, or whether standard element-color assignments are used. These are material behavioral details missing.

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 that clearly states the core function with no redundant words. It is front-loaded with the action and target.

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 simple one-parameter utility, the description plus schema cover the basic functionality and selection default. However, lack of usage guidance and behavioral details (e.g., overriding existing colors) leaves it minimally complete. Output schema presence reduces the need to describe return values.

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 single 'selection' parameter is fully described in the schema ('What to recolour. Defaults to everything.'), so the schema already covers parameter semantics. The tool description adds no parameter-specific information beyond the schema, warranting the baseline score of 3.

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 uses a specific verb ('Colors') and resource ('atoms') with a clear method ('by their element'), distinguishing it from generic sibling tools like 'color' or 'util_color_secondary'. It directly explains the tool's function.

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 'color', 'spectrum', or 'util_color_secondary'. There is no mention of selection scoping or prerequisites. The description simply states the action without contextual direction.

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