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

Annotations only declare safety hints (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true). The description adds real behavioral context beyond them: no facial identification is performed, images are not stored, and the call has a flat $0.05 cost. The billing side effect also helps explain the readOnlyHint=false flag rather than contradicting it.

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 sentences, front-loaded with what the tool does, then privacy and pricing facts. Dense but every clause carries information; no filler or restated boilerplate.

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, return values need not be explained. The description covers method, input limits, privacy, and cost, which is sufficient for invocation; the only gap is routing guidance against sibling analysis tools.

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 baseline is 3. The description reinforces two parameter constraints — the 1-3 image limit and the recommendation for differing lighting across photos — which maps to the 'images' array, but adds no syntax or format detail beyond what the schema already states.

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 states a specific verb and resource ('Personal color analysis from 1-3 portraits') and details the mechanism (CIELAB/ITA pixel colorimetry plus vision-model cross-check producing a 4-season verdict). This clearly differentiates it from siblings like portrait_precheck, style_profile, and style_report.

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 described pipeline and the '1-3 portraits' input constraint, but the description never says when to pick this over portrait_precheck or style_profile, nor does it state exclusions or prerequisites. An agent must infer routing from sibling names alone.

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