crm_delete_contact

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

The description goes far beyond the annotations (readOnlyHint: false, destructiveHint: true, idempotentHint: true, openWorldHint: true) by disclosing the soft-delete nature, required OAuth scope ('crm.objects.contacts.write'), idempotent behavior, cache invalidation, and not-found error handling. This gives the agent a full understanding of side effects and prerequisites.

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 front-loaded with a clear one-sentence summary, followed by usage guidance, behavioral details, permissions, and error cases. Each sentence adds unique value; there is no fluff or repetition. Despite being a bit long, it's well-organized and efficient for a destructive tool.

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?

Given the tool's simplicity (one parameter), the description covers all critical aspects: purpose, when to use, safety, permissions, idempotency, cache effects, and error behavior. The output schema exists, so return details are not needed. This is thoroughly complete for an agent to safely invoke the tool.

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 fully describes contact_id as 'HubSpot contact record id, as returned by search, list, or create,' achieving 100% schema description coverage. The description adds no new parameter semantics beyond noting that an unknown id raises a not-found error, which is minor.

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 'Archive (soft-delete) a HubSpot contact so it drops out of active views,' which precisely states the action (archive/soft-delete), resource (HubSpot contact), and effect. It clearly distinguishes from sibling tools like crm_get_contact or crm_update_contact by focusing on deletion behavior.

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?

Explicitly says 'Use this instead of asking a human to delete in the UI,' giving a clear when-to-use directive. It also notes the tool 'never issues a hard delete' and that records are restorable for a limited window, which helps the agent decide if this is appropriate for the task.

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