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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered by structured data. The description adds one genuine piece of context not in the annotations: only 'owned' creatives can be deleted. However, it omits whether deletion is permanent/irreversible and whether any confirmation or auth scope is required, which matters for a destructive operation.

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?

A single compact sentence that front-loads the verb and resource with no filler. It is efficient, though the brevity contributes to the semantic gaps noted elsewhere rather than being purely a virtue.

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?

For a destructive mutation, the definition leaves out irreversibility, required scope/ownership verification, and any explanation of the connection_context parameter. An output schema exists so return values need not be described, but the missing behavioral and parameter context still leaves the agent under-informed.

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 0%, so the description must carry parameter meaning, and it largely does not. It references 'selection key' but gives no format or semantics, and 'creative reference' is confusingly introduced as an alternative even though the schema exposes only selection_key and connection_context. connection_context is never mentioned.

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 gives a specific verb+resource ('Delete one owned creative') and narrows scope to a single owned entity, which distinguishes it from sibling read/list tools like creatives_get and creatives_list. It stops short of explicitly differentiating from other mutating siblings such as creatives_abandon_upload, but the purpose is 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?

There is no when-to-use guidance, no statement of prerequisites, and no mention of alternatives (e.g., whether abandoning an upload is preferable for in-flight creatives). The agent gets no criteria for choosing this tool over other creatives_ operations.

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