ad_manager_fb_delete_page

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a destructive operation. The description does not add any additional behavioral context beyond the annotation, such as irreversibility, side effects, or what exactly is disconnected. It is consistent with annotations but adds no value beyond them.

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 concise with a single sentence stating the action. This is appropriately sized for a simple delete operation, and there is no unnecessary verbosity. The action is front-loaded, making it easy to scan.

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 description is minimal and lacks important context for a destructive operation. It does not explain what the deletion entails (e.g., disconnecting the page from the ad account), nor does it indicate any side effects or confirmations. With no output schema, the agent gets no hint about the response. Given the tool's destructive nature, more context is needed to ensure safe and correct invocation.

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 provides full descriptions for both parameters (pageId and locationId), and schema coverage is 100%. The description adds nothing about parameters, so the baseline of 3 applies per the rubric.

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 states a clear verb (delete) and resource (page connection). It distinguishes from sibling delete tools by specifying 'page connection' rather than ad, campaign, etc. However, it is terse and does not elaborate on what a 'page connection' entails, so it is clear but not highly descriptive.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives, nor any exclusions, prerequisites, or conditions. An agent receives no help in deciding when this tool is appropriate.

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