util_cbas

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

No annotations are provided, and the description is too brief to disclose any behavioral traits beyond the name. It does not mention side effects, prerequisites, or what happens to the scene when invoked.

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 extremely concise but at the cost of clarity. It is a single phrase that does not provide enough information to be useful. It is under-specified rather than appropriately concise.

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?

Given the tool has a parameter and an output schema, the description is completely inadequate. It does not explain what the output represents or how the tool behaves, leaving the agent with insufficient context to invoke 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?

The input schema has one optional parameter 'selection' with default 'all', but the description does not explain its meaning or role. With 0% schema description coverage, the description fails to add any value beyond the schema.

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 by atom, salmon carbons (Color By Atom, Salmon)' gives a vague hint that the tool colors atoms with a salmon color for carbons, but it lacks a clear verb or resource. It does not explicitly state what the tool does, and it is ambiguous compared to more explicit siblings like 'util_color_by_element'.

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. With a large set of sibling tools covering various coloring and visualization functions, the description gives no context for appropriate use.

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