Delete campaign

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Delete a campaign by id' with no mention that deletion is permanent, irreversible, may cascade to associated data, or require specific permissions. This is a critical omission for a destructive operation.

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 a single sentence that front-loads the action and resource, with no redundant words. It is perfectly concise, though this conciseness comes at the cost of substance.

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 delete tool with no annotations, no output schema, and a single parameter, the description is severely incomplete. It lacks any mention of side effects, prerequisites, confirmation steps, or error handling. An agent cannot understand the full impact of calling this tool, especially since it is destructive.

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?

With schema description coverage at 0%, the description must explain the parameter. It merely says 'by id', which clarifies that campaignId is the identifier but does not explain how to obtain it, its format, or any constraints. It adds minimal value beyond the schema's property name.

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 verb 'delete' and resource 'campaign', and explicitly identifies the parameter by id. It distinguishes from sibling campaign tools (get, create, update, run, etc.) because it is the only delete operation for campaigns. However, it is terse and doesn't add any nuance beyond the title.

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 given on when to use this tool versus alternatives. It is implied that deletion is the use case, but there are no conditions, prerequisites, or exclusions. The description does not mention that deletion is irreversible or that it might be better to archive instead.

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