Color (destructive)

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

Annotations already declare destructiveHint=true and non-idempotent, so the safety bar is lower, yet the description still adds real behavior: the first call returns a plan plus confirm_token and must be repeated to apply, and per-action consequences are disclosed (target grades overwritten, group clips become ungrouped). It does not mention permissions or irreversibility beyond the token gate.

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 front-loaded sentence and bulleted action list are efficient and scannable, but the confirm_token/batch_run guidance sits after the bullets rather than up front, and the trailing 'describe_action' reference partially duplicates the params already listed.

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 destructive, multi-action, nested-payload tool, the description covers actions, per-action required params, the plan/confirm workflow, and the batch alternative; dry_run/snapshot semantics and the return shape are handled by the schema and output schema. A mention of snapshot recommendation for irreversible reset_all_grades would make it complete.

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% giving a baseline of 3, but the description goes further by naming the required params per action (source*/targets*, name*, item*/name*, target) inside an `op` object that permits additionalProperties. This meaningfully fills in the nested payload the schema only gestures at.

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 ('Remove') and resource ('color objects') and enumerates the four destructive operations, so an agent knows this is the deletion counterpart to color_read/color_write. It never explicitly says 'use color_write for non-destructive changes', but the action list makes scope unambiguous.

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 routes bulk/known-in-advance sequences to batch_run instead of repeated calls, and the confirm_token instruction defines the two-step invocation. There is no explicit statement of when to prefer color_write over color_delete, but the destructive framing covers the main selection decision.

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