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

With no annotations, the description carries the burden. It discloses a flat fee of $0.05/call, required photo counts, and the analytical sources (colorimetry consensus, published geometry rules). It does not mention authentication or error handling, but the pricing and input constraints are useful behavioral context.

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 description is two sentences that pack a lot of information without redundancy. It front-loads the core purpose before diving into specifics.

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?

Despite having no output schema, the description outlines what the verdict contains (color, face-impression, body frame, integration rules), giving the agent a clear sense of the return value. It also states pricing and input requirements. It lacks explicit output structure, but for a complex tool this is a reasonably complete overview.

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 schema has only 14% description coverage, so the description must compensate. It clarifies that images should be face photos (1-3), body_image_url is for full-body, and questionnaire is optional, which adds value beyond the raw schema. However, parameters like style, image_url, and image_base64 are not addressed in the description, leaving some ambiguity.

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 clearly specifies the tool's function as an integrated styling verdict, enumerating its components (seasonal color, face-impression zone, body frame, integration rules). This distinguishes it from sibling tools like portrait_analysis or style_report by emphasizing the integrated nature and specific inputs.

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?

The description provides context on when to use (when an integrated verdict is desired) and input requirements (1-3 face photos, optional full-body+questionnaire). It does not explicitly reference alternatives or situations where a sibling tool would be preferred, but the integrated scope implies its use case.

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