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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false. The description adds meaningful behavior beyond those annotations: it resolves the subject internally, must be called exactly once per subject, must not open extra product UIs, and must explain returned limitations instead of inventing pairs.

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 front-loaded with purpose and examples, then moves into operational constraints, alternative routing, parameter usage, ambiguity handling, and limitations. It is longer than typical and includes some repeated guardrails, but the structure is clear and most sentences carry useful routing or behavioral information.

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?

Given the output schema and annotations, the description is complete for this render tool: it covers intended use, alternatives, subject resolution, ambiguity, call limits, fallback behavior, and what not to substitute. The only notable gap is buyer_context, which is optional and does not undermine correct invocation.

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 already documents query and product_id in detail, and the description mainly reinforces the product_id-over-query preference plus internal subject resolution. However, buyer_context has no description in either the schema or the tool description, leaving one of three parameters undefined.

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 action: render Complete the Look with store-configured complementary and supplementary products for a subject product. It clearly distinguishes this from product search, product detail, and general styling answers, so an agent can identify the tool without opening the schema.

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?

It gives explicit when-to-use conditions, many shopper phrasings, follow-up request handling, call-count rules for one versus multiple subjects, exclusions such as not calling automatically after discovery search, and the alternative render_product_search for general suggestions. Ambiguous 'this/it' handling is also specified.

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