util_rainbow

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Colors residues' but omits details such as whether colors are applied to all objects, if existing coloring is overwritten, what exactly 'rainbow' means (e.g., color sequence), or any side effects.

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, front-loaded sentence of 7 words with no extraneous information. It efficiently conveys the core purpose.

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 (presumably explaining returns), the description is too sparse for a tool with no annotations. It fails to specify the color scheme, whether it acts on the current selection or entire structure, or how it differs from similar sibling tools like 'util_chainbow'. Critical usage context is missing.

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 sole parameter 'selection' has no description in the schema (0% coverage) and the tool description does not explain it. The agent cannot infer valid formats, how 'all' is interpreted, or whether it accepts complex selections. The description adds no value beyond the schema's bare property definition.

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 'Colors residues in rainbow from N to C terminus' clearly states the tool's action (colors), resource (residues), and specific scope (rainbow gradient along the backbone). This distinguishes it from siblings like 'color' (solid color) and 'spectrum' (color by property) and 'util_chainbow' (color chains).

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 offers no guidance on when to use this tool versus alternatives like 'spectrum' or 'util_chainbow'. There is no mention of prerequisites, context, or scenarios where this tool is preferred or not recommended.

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