delete_campaign_assignment

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

With no annotations, the description must communicate behavioral details, but it only says 'Delete a campaign assignment'. It does not disclose whether the deletion is permanent, whether there are side effects (e.g., removing related records), permission requirements, or any error conditions.

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, containing a single sentence with no unnecessary filler. It could be more informative, but for a one-parameter delete operation, this brevity is acceptable and not wasteful.

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 simple (one required parameter, no output schema, no annotations), so a minimal description is somewhat viable. However, the description lacks context about the deletion's effects, return values, or how it differs from the several similarly named sibling tools, making it only minimally 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?

The schema already documents the single 'id' parameter with 100% coverage as 'Campaign assignment ID'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline but does not exceed it.

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 action ('Delete') and resource ('campaign assignment'), making the primary purpose obvious. However, it does not distinguish this tool from similarly named siblings like 'vast_delete_campaign_assignment' or 'vast42_delete_campaign_assignment'.

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 guidance is provided on when to use this tool versus alternatives such as 'update_campaign_assignment', 'list_campaign_assignments', or the namespaced delete variants. The description simply states the action without explaining preferred use cases or exclusions.

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