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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether removal is permanent or recoverable, what happens to the piece's content, or whether other pieces are reordered or affected. For a destructive tool this is a notable gap even with a lower bar.

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?

Three words with zero waste and the action front-loaded, so nothing needs trimming. But the brevity is under-specification rather than efficiency; there is no structure beyond a bare verb phrase to guide an agent handling an irreversible operation.

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?

This is a destructive deletion tool with no output schema, and the description does not explain the consequences of the call, recoverability, or how the targeted piece is scoped within a document. Annotations cover safety flags, but an agent still cannot tell from the definition what will actually happen after the call succeeds.

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%, with both document_id and name documented in-schema, including an example set of names. The description contributes nothing about the parameters, so the baseline of 3 applies. Identifying scope by document_id and piece name is well covered by the schema itself.

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?

"Remove a piece" gives a specific verb and a resource name, so the basic action is identifiable. However, "piece" is never defined (an ad creative? an ad-group element?) and nothing distinguishes this from siblings like ads_edit_piece, ads_read_piece, or deck_delete_slide. The agent must infer what a piece is and where it lives from the required document_id alone.

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 mention of alternatives such as ads_edit_piece for modification instead of removal, and no stated preconditions (e.g., whether the document must be opened first). The agent is left to infer usage entirely from the tool name.

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