util_cbao

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It mentions the coloring outcome but does not state whether existing colors are replaced, whether non-carbon atoms are also recolored, or how the selection parameter affects the operation. This is minimal and leaves key behaviors unspecified.

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 concise phrase with no unnecessary words, front-loading the action and color. The parenthetical is a brief clarification that adds value without bloat, making it highly efficient for the agent to parse.

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 tool with one well-documented parameter and an output schema, the description conveys the core functionality. However, it lacks usage context relative to the many sibling color utilities and does not fully clarify the exact effect on all atoms (e.g., whether non-carbon atoms get recolored), leaving some ambiguity.

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 100% and the parameter 'selection' is clearly described ('What to recolour. Defaults to everything.'). The tool description adds no additional semantic detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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 the action ('Colors by atom') and the specific resource ('orange carbons'), which distinguishes it from sibling color utilities by color. The parenthetical '(Color By Atom, Orange)' reinforces the intent, though it could be more explicit that it colors all atoms by element with an orange carbon override.

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 util_cbc or util_cbag. The description simply states what it does without mentioning contexts, prerequisites, or exclusions, leaving the agent to infer usage from the name and description.

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