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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds a non-obvious behavioral limitation: this tool produces a quote, not a generated asset. That 'Does not generate' caveat is useful context beyond the safety annotations and does not contradict them.

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?

Two short sentences with no waste. The first sentence front-loads the action and resource, and the second sentence earns its place by dispelling a likely generation expectation. Nothing is redundant with the schema or annotations.

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?

Strong structured context—100% schema coverage, an output schema, and read-only annotations—makes the sparse description adequate for invoking the API call correctly. However, the description leaves the meaning of 'quote' and the relationship to the quote_ad_explain/studio/proof_pack/tip_pack siblings implicit, which is a notable gap given the large sibling cluster.

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 input schema covers 100% of the parameters, including the meaning of count, the valid layout aspects, and the companyId provenance from import_ad_website. The description adds no parameter-level detail beyond the schema, so the baseline score applies.

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 uses a specific verb ('Quote') and a specific resource ('Ad Lab layout') and adds a scope limitation ('Does not generate') that separates it from the generate_ad family. However, it does not differentiate among the many quote_ad_* siblings such as quote_ad_explain, quote_ad_proof_pack, quote_ad_studio, and quote_ad_tip_pack, so the agent must rely on the tool name for that distinction.

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 implies the tool is for quoting Ad Lab layouts, and the 'Does not generate' clause gives a when-not signal that should steer agents toward generate_ad for actual generation. It does not explicitly name alternatives or specify when to choose quote_ad over its quote_ad_* siblings, so routing guidance is mostly implied rather than stated.

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