Generate ad hooks

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

With no annotations, the description carries the full burden and does reasonably well: it discloses cost ('Metered at the API rate'), that no new search is performed, and the shape of the output (callout + loop/promise). It omits auth/permission needs and polling semantics, though the schema's wait_seconds description partially covers the latter.

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?

Three dense sentences, each earning its place: purpose and grounding first, then cost/wait behavior, then the steering parameter. No filler or restatement of the name.

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?

No output schema exists, and the description compensates by describing what a hook contains and that results are grounded in real comments, plus metering and wait behavior. Coverage of count semantics and rate-limit specifics is thin, but nothing critical to correct invocation 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 75%, so the schema already documents search_id, angle, and wait_seconds; the description's 'angle to steer (a product, a persona, a platform)' adds modest meaning over the schema's example. It adds nothing for `count`, whose schema entry has no description.

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?

States a specific verb (write ad hooks) and resource (hooks) grounded in a named source (a completed search's quotes), and describes the output mechanics (callout from real comments plus a loop or promise). This clearly separates it from siblings like search, get_quotes, and ask.

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 establishes the precondition (needs a completed search's quotes / a search_id) and explicitly notes 'no new search,' steering an agent that needs fresh data elsewhere. It does not, however, name a direct alternative (e.g., use search first, or ask instead) for ambiguous cases.

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