delete_contact_profile

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

The description adds context about the permanent and mutating nature beyond the destructiveHint annotation. It does not contradict annotations. However, it omits details such as required permissions or cascading effects.

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 sentences effectively convey purpose, warning, and usage. No unnecessary words; the warning is front-loaded.

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 a dry-run safety, the description is nearly complete. It lacks return value details, but no output schema exists. Sibling context is sufficient.

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 covers 100% of parameters with descriptions. The description reiterates the dryRun parameter's role, adding a warning but not new semantic meaning beyond what the schema already provides.

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 'Deletes a Cognigy.AI contact profile', specifying the verb and resource. It distinguishes itself from sibling tools like create_contact_profile or get_contact_profile by its destructive action.

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 explicitly warns about permanent removal and instructs to set dryRun=false to actually delete, implying dryRun=true for validation. However, it does not mention when to use alternatives like merge_contact_profiles or update_contact_profile.

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