ad_manager_fb_delete_ad

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'Delete ad' is consistent but adds no new behavioral context. It does not mention permanence, cascading effects, permission requirements, or any side effects beyond the bare action. With annotations carrying the safety profile, the description adds minimal value.

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 extremely short, but this is under-specification rather than effective conciseness. It omits necessary context that a destructive operation with an ambiguous resource identifier requires. The brevity does not serve the agent's decision-making.

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 tool with no output schema and a description that only says 'Delete ad', the agent lacks essential information: what an 'ad' is in this context, what happens on success, whether the deletion is permanent, and what the effects are. The description is inadequate for the complexity of the operation.

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 description says nothing about the parameters. The input schema covers only 50% of parameters with descriptions (locationId), while adId is undocumented. The description does not compensate for this gap, leaving the agent without guidance on what adId refers to or how locationId affects the operation.

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 'Delete ad' states a verb and a resource, but it is essentially a restatement of the tool name 'ad_manager_fb_delete_ad'. It adds no distinction among the many sibling delete tools (e.g., delete_adset, delete_campaign, delete_ad_account), so an agent cannot tell which entity is being targeted beyond the name itself.

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 guidance on when to use this tool versus alternatives. No context about prerequisites, whether a specific integration/account must exist, or when one might prefer a pause or update instead of delete. The description provides zero usage direction.

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