draft_structured_snippets

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

Annotations indicate it is not read-only (readOnlyHint: false) and not destructive (destructiveHint: false). The description adds that it returns a PREVIEW, implying no final creation or side effects, which is significant behavioral context beyond 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 a single sentence containing essential information: action ('draft'), resource ('structured snippet assets'), and key outcome ('returns a PREVIEW'). It is concise and front-loaded, though adding minimal parameter context would not sacrifice brevity.

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 3 parameters (2 required) with no schema descriptions, the description is incomplete. It does not explain the format of the 'snippets' array or the role of 'customer_id'. The existence of an output schema partially mitigates missing return info, but input semantics remain unclear.

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 0% with no descriptions for any parameter. The description only names the tool's purpose and does not explain the structure or constraints for 'snippets' or the optional 'customer_id', leaving the agent to infer from parameter names 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 clearly states it drafts structured snippet assets for a campaign and returns a preview. It distinguishes itself from sibling draft tools (e.g., draft_callouts, draft_sitelinks) by specifying 'structured snippet assets', making the 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?

The description provides no guidance on when to use this tool versus alternatives like draft_callouts or draft_sitelinks. No context for prerequisites or when to choose this over other drafting tools is given.

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