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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false. The description adds valuable context beyond that: it refreshes in-flight jobs and does not charge. These are useful behavioral traits, though the 'refreshes' side-effect wording sits slightly awkwardly with readOnlyHint (not a full contradiction).

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?

Three short, front-loaded sentences with zero waste. The primary purpose and behavioral caveats are presented efficiently.

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, full parameter descriptions, and rich annotations, the description is complete enough for selection and invocation. It covers purpose, ordering, refresh behavior, and cost, leaving only minor usage-competition details to inference.

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 description coverage is 100%, so the schema already documents op, limit, and cursor. The description adds no parameter-specific meaning beyond what the schema provides, making the baseline 3 appropriate.

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 ('List'), resource ('Paint Lab AI results'), scope ('this account's'), and ordering ('newest first'). Clearly distinguishes from get_paint_lab_generation (singular) and other list_* siblings by its resource.

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?

Usage is implied by the listing description, but no explicit when-to-use guidance or alternative tools are named. The 'Refreshes in-flight jobs' line hints at a reason to call, but it doesn't say when to prefer this over get_paint_lab_generation or other siblings.

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