hires_delete_nurture_campaign

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It discloses that the delete is a soft-delete and that active executions will be stopped, which are important side effects. It could further detail reversibility or permissions, but the disclosed traits are highly relevant and non-obvious.

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 two concise sentences, front-loading the action ('Delete') and immediately clarifying the key qualifier ('soft-delete'). It then adds one important behavioral detail. No redundant words or repetition of schema data.

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 simple delete tool with one parameter and no output schema, the description covers the essential context: the soft-delete nature and the impact on active executions. It could mention error handling or idempotency, but given the tool's low complexity, the description is adequately 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 input schema already provides 100% coverage, describing 'id' as 'Nurture campaign ID'. The description adds no additional parameter meaning, but given the schema is self-sufficient, 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 states the verb 'Delete' and resource 'nurture campaign' clearly, and distinguishes it from other nurture campaign tools by specifying 'soft-delete' and the effect on active executions. This is a specific and unambiguous purpose that differentiates it from get/update/list operations.

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 description provides clear context for when to use this tool (to delete a nurture campaign) and adds behavioral guidance by noting that active executions will be stopped. It does not explicitly mention alternatives or exclusions, but the context is sufficient for a delete operation.

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