delete_advertiser

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It simply restates the tool's function without revealing whether the deletion is permanent, what cascading effects occur, or what permissions are required, leaving the agent uninformed about the tool's actual behavior.

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 short sentence with no wasted words, but it is under-specified for a delete operation. It lacks essential context such as consequences and usage guidance, making the conciseness more indicative of incompleteness than effective 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?

The tool is a delete operation with a single parameter, but the description omits critical context about reversibility, downstream effects, and distinction from archiving. This makes it incomplete for an agent to safely and correctly invoke the tool.

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 input schema fully documents the only parameter 'id' with a description ('Advertiser ID'), so schema coverage is 100%. The description adds no additional meaning beyond what the schema already provides, and a baseline of 3 is appropriate.

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 verb 'Delete' and the resource 'advertiser', making the core purpose unambiguous. It does not, however, distinguish this from related operations like archive_advertiser, so it lacks sibling differentiation.

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 such as archive_advertiser or other deletion methods. There is no mention of prerequisites, soft-delete versus hard-delete, or any distinguishing conditions.

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