util_cbag

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

Annotations are absent, so the description must carry the full burden. It discloses no behavioral traits such as whether the coloring modifies the view permanently, if it is reversible, or any side effects. The minimal text does not help an agent understand the tool's impact.

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, but it underspecifies the tool's behavior. It is too concise for the information needed, lacking necessary details about the coloring scope and parameter usage.

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?

Despite having an output schema, the description does not explain what the tool returns or how it modifies the molecular view. For a tool with a single parameter and many siblings, the description is insufficient for an agent to use it correctly.

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 0%, and the description does not mention the 'selection' parameter. The parameter has a default of 'all' but no semantics are provided, leaving the agent unaware of how to control the scope of the coloring.

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 states 'Colors by atom, green carbons', which indicates the tool colors atoms with green for carbons. However, it does not specify the behavior for other atom types, and the meaning of 'color by atom' is ambiguous. It does not distinguish from sibling tools with similar names.

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 on when to use this tool over siblings. The long list of sibling tools with similar naming (e.g., util_cbac, util_cbab) provides no differentiation, and the description offers no context about when this specific coloring scheme is appropriate.

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