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

With readOnlyHint=true and destructiveHint=false, the safety profile is already covered by annotations. The description adds beyond that by clarifying the tool does not generate contentched and by documenting default behavior (6 slides at 4:5) and the uniquePlates reuse behavior. This gives the agent a clear picture of what the quote represents without contradicting the 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 compact and well-structured: a clear purpose statement, an important behavioral exclusion, then the key defaults and option behavior. Every sentence adds value and there is no padding or repetition of structured fields.

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 exists to document return valuesency and annotations cover safety behavior, the description is complete for selecting and invoking the tool. It explains defaults, aspect ratio options, uniquePlates behavior, and the no-generation guarantee. No critical operational detail is missing.

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 adds minor context by noting 'distinct topic-matched image' for slides and restating the default slide count and aspect ratio, but it does not meaningfully enrich parameter understanding beyond what the schema already provides.

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 begins with a specific verb ('Quote') and a precise resource ('Ad Lab tip pack'), making the tool's purpose immediately clear. The explicit statement 'Does not generate' distinguishes it from the generate_ad_tip_pack sibling and other generation tools, so an agent can select it correctly based on intent.

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 context is clear: this tool is for quoting a tip pack, not generating one, and 'Does not generate' provides an explicit exclusion. However, it does not name an alternative tool or describe scenarios such as 'use generate_ad_tip_pack when you need actual assets,' so the guidance is good but not fully explicit.

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