Recolor project

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

No annotations are provided, so the description carries full responsibility. It discloses that the operation also retints open panes within the project, which is a notable side effect beyond the schema. It also qualifies the project as 'remembered', implying only stored projects are eligible.

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?

Two short sentences that front-load the action, include necessary context (id lookup and side effect), and contain no wasteful words.

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 simple two-parameter mutation with no output schema, the description covers all necessary aspects: target, input format, id acquisition, and side effect. It is sufficient for an agent to select and invoke the tool 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 description adds meaning to the id parameter by explaining how to obtain it via list_projects, and provides a concrete hex color example. The schema only describes color as a hex string, so the description enriches both params.

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?

Clearly states the action (set color), the target (remembered project's frame/dot color), and the required input (hex color). It also distinguishes from recolor_pane by operating on projects, and the side effect of retinting panes is noted.

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?

Provides a direct pointer to list_projects for finding ids, and specifies the color format. It implies the tool is for project-level recoloring as opposed to pane-level (recolor_pane exists as a sibling), but does not explicitly contrast alternatives.

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