draft_update_rich_media_ad_item

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

With no annotations, the description carries full burden for behavioral disclosure. It merely restates the mutation without adding any details about side effects, partial vs. full update semantics, permissions, or response behavior. There is no additional context beyond the tool name.

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 with no wordiness. It is efficient but lacks any structured formatting or additional helpful sections. It earns its place but is minimal.

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?

The tool updates a complex entity, has a free-form 'draft' object parameter with no defined schema, no output schema, and no annotations. The description gives no information about which fields can be updated, how the draft object should be structured, or what the return value is. This is inadequate for an agent to use correctly.

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 100% for the two parameters, so the baseline is 3. The description does not add any elaboration on the 'draft' object's fields or the meaning of 'id'. The schema already provides the minimal descriptions.

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 the action ('Update'), resource ('rich media ad item'), and scope ('draft'). It distinguishes itself from create/list/get/delete siblings and from the non-draft update_rich_media_ad_item by including 'draft'.

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?

No guidance is provided on when to use this tool vs. alternatives. It does not mention prerequisites, whether the draft must already exist, or when one might prefer the live version update. The only implied usage is literal reading of the verb 'update'.

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