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

Annotations already state readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds authentication specifics (token types, Bearer session) and clarifies the verify parameter triggers external fetch. No contradictions with annotations, and it goes beyond the schema by explaining behavior.

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?

Description is a single, information-dense sentence with parentheticals. It is front-loaded with the primary purpose and includes necessary auth details without excessive verbosity. Could be slightly more concise but each clause serves a purpose.

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?

Covers authentication prerequisites, availability timing, and optional verification behavior. While no explicit return format is mentioned, the description sufficiently covers the tool's functionality given no output schema exists. The inclusion of placement guidance adds value.

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 coverage is 100% but description enriches both parameters: explains token formats (at_..., sk_...) and that a Bearer session also works, and explains verify=true triggers a check. This adds clarity not present in schema alone.

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 explicitly states it retrieves the exact script tag and ad-unit markup, clearly distinguishing it from sibling tools like apply or ad_settings. The verb 'Get' plus specific resource makes purpose unambiguous.

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?

Provides explicit guidance on when to use (available immediately after apply), authentication methods (token or Bearer session), and when to use verify=true. It also advises against asking users to paste tokens when session already authenticates, effectively excluding misuse.

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