Delete Contact

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

No annotations are provided, so the description carries the full burden. It warns 'This action cannot be undone' and discloses that 'the contact and all associated data will be removed,' covering irreversibility and cascade deletion. This is strong behavioral transparency 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 concise: it states purpose, includes a prominent warning, and gives a clear prerequisite in under 50 words. Every sentence is purposeful and information 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?

With only one required parameter and no output schema, the description addresses all key operational concerns: irreversible deletion, scope of data affected, and how to obtain a valid contact_id. No significant gaps remain for likely use cases.

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 fully documents contact_id with its own description, and the description reinforces that it is required while guiding valid ID discovery. This adds meaningful operational context beyond the schema's basic type/name information.

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 opens with 'Permanently delete a contact or company from Less Annoying CRM', giving a specific verb and resource. It clearly distinguishes this from sibling delete tools by naming the target and emphasizing permanence.

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 states 'Required: contact_id' and instructs users to 'Use search_contacts or get_contact to find valid contact IDs before deleting,' providing clear preparation guidance. It does not explicitly contrast with sibling delete tools, but the prerequisites and context are clear.

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