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

Beyond the annotations, the description discloses that it writes to Studio, creates billable AI usage, is synchronous, forbidden as task, has multiple mutation modes, partial failure policy, permission requirements for seat selection, and deterministic retry behavior. This far exceeds annotation coverage.

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 repeats the title nearly verbatim, uses a stray '..', and appends a long series of policy statements without clear structure. While dense, it is not concise and front-loads only the first sentence before a sizable block of instructions.

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 complexity (27 params, output schema present, annotations), the description provides substantial behavioral context: mutation modes, failure policies, auth requirements, retry logic, and response presentation rules. However, the mismatch between 'saveToStudio' in the description and 'persistence' in the schema, plus minimal coverage of most parameters, prevents a perfect completeness score.

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 schema has 0% description coverage across 27 parameters, so the description must compensate. It explains the role of creativeIds, saveToStudio (persistence), seatId/seatName, and idempotencyKey, but leaves the majority of parameters (brief, input, assets, audience, campaign, template, etc.) undescribed, adding limited meaning for the full parameter set.

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?

Description opens with a clear verb+resource: 'Generate Studio-ready design briefs for one or more creatives,' and specifies the inputs (campaign context, brand rules, audience, offer, format constraints). It also distinguishes the conditional save behavior, separating it from purely read or versioning tools.

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 gives clear context on when the tool saves vs proposes ('When creative IDs and saveToStudio are supplied... otherwise returns a non-destructive proposal'), and lists mutation modes (validate_only, preview_only, execute). However, it doesn't explicitly name sibling alternatives or state 'use instead of X', so not a full 5.

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