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

Annotations already declare readOnly/idempotent/non-destructive behavior, and the description adds valuable context: it composes a full capsule, applies a stylistic constraint (bleu eau/aqua remains light/cool, no black satin), and defines a fallback when the color is not in the catalogue. No contradiction with annotations.

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 three sentences with the main action front-loaded and no filler. Every sentence contributes either the core behavior, a style guardrail, or the fallback behavior.

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 and readOnly annotations, basic calls are supported, but the description does not explain how optional style parameters affect the recommendation and does not route the agent away from recommend_weather_look or shop_the_look. It is usable but not fully complete for a tool with 8 parameters and several close siblings.

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 only 13%, so the description must compensate. It adds meaningful color and material semantics (bleu eau/aqua, satin noir) and implies the piece-driven capsule, but it leaves season, audacity, occasion, detail_level, and include_conversion unexplained.

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: 'Je compose une silhouette complète' and enumerates the output components (look nommé, capsule, pièce, ancre, chaussures, sac, un bijou). This distinguishes it well from weather-specific or shopping-focused sibling tools like recommend_weather_look and shop_the_look.

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?

There is no guidance about when to use this tool versus its siblings; recommend_weather_look, weather_looks, and shop_the_look are not mentioned. The color fallback rule is an execution behavior, not a tool-selection criterion.

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