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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description usefully adds the auth prerequisite (write scope), but leaves the key ambiguity unresolved for a destructive operation: whether it removes the profile only from the campaign or deletes the profile entity itself, and whether the change is reversible.

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?

Two short sentences, action first and prerequisite second, with no redundant or filler wording. Everything present earns its place.

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?

Parameters are fully covered by the schema and no output schema is needed, but for a destructive mutation with no undo information the description should clarify the blast radius (association removal vs entity deletion) and any irreversibility. That gap keeps it at minimum-viable rather than complete.

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 'id' (campaign ID) and 'profile_id' (target profile ID) documented in the schema. The description adds no extra meaning about how those two identifiers interact or any constraints, so the baseline 3 applies.

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?

States a specific verb ('delete') and resource ('target profile') and scopes it to a campaign, which is enough to separate it from delete_audience, delete_campaign, and create_target_profile. It stops short of explicitly contrasting with any sibling, so a 4 rather than a 5.

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 only guidance is the prerequisite 'requires write scope'; there is no statement of when to use this versus alternatives (e.g. detaching a profile vs deleting it outright) and no exclusions or warnings about conditions under which it should not be called.

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