delete_marketing_engagements

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

With no annotations provided, the description carries the full burden. It discloses that data is 'Marks data such that it no longer appears in reports' (a soft-delete behavior), requires a specific scope, and cannot delete activity-level data. This is meaningful context beyond the name, though it does not clarify irreversibility or side effects on related data.

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 concise and front-loaded: it leads with the core action, then provides the important soft-delete nuance, an explicit alternative for activity-level data, and the required scope. Each sentence adds value with no fluff.

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?

Given no output schema and no annotations, the description covers purpose, behavioral nuance, limitation, and auth requirement. It lacks details on parameter selection (e.g., how channelHandle and deleteEngagementsForAllChannels interact) and reversibility, but these are minor given the schema covers parameter semantics.

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%, so the schema already documents both parameters (channelHandle and deleteEngagementsForAllChannels) with clear descriptions. The tool description adds general scope context but does not explain parameter interactions, so the 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 'Delete all channel-level marketing engagement data' with a specific verb, resource, and scope. It also distinguishes from activity-level deletion by noting 'Activity-level data cannot be deleted directly - delete the MarketingActivity instead,' which sets it apart from sibling tools like delete_marketing_event.

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?

Explicitly explains when not to use this tool (for activity-level data) and directs the user to an alternative: 'delete the MarketingActivity instead.' It also states the required scope 'write_marketing_events,' providing clear context and prerequisites.

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