Color (read)

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the per-action caveats: validate_dctl is 'sensitive to formatting: one-line functions can fail', and list_versions distinguishes local vs remote versions. These are real behavioral notes beyond the annotations, though nothing is said about latency, cost, or error modes.

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?

Front-loaded with the purpose in one sentence, then a tight bulleted action list with no filler. Minor deduction for the slightly cryptic header 'op.action (params; * = required)', which requires an extra read 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?

With an output schema present and annotations covering safety, the description only needs to disambiguate the action space, which it does for all four enum values. Small gaps remain, such as list_color_groups mentioning 'in a timeline' without declaring a timeline parameter, and no note on whether remote version listing needs extra auth.

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 coverage is 100%, but the schema's op object is a free-form bag with additionalProperties, so the description is doing the real work: it maps each action to its expected parameters (target, item*, source/path) and marks required ones with '*'. Individual parameter meanings (e.g. what 'source' vs 'path' contain in validate_dctl) are left implicit.

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?

States a specific verb and resource ('Read color state') and immediately enumerates the four concrete actions it performs, so an agent knows exactly which sub-operations are reachable. The sibling set splits read/write/delete by suffix, and the 'no side effects' framing cleanly separates it from color_write and color_delete.

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?

Explicitly gives the two intended use cases: 'find ids and check results', which is actionable guidance for an agent. It does not name color_write as the alternative for mutations or state any exclusion, so it falls short of a full when/when-not statement.

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