Delete HubSpot Contact

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

The description adds value beyond annotations by specifying 'soft-delete' and 'recycle bin' behavior. Annotations already indicate destructiveHint: true, but the description clarifies the nature of destruction as reversible, which is helpful. It does not contradict annotations.

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 extremely concise: two sentences for the main function, one line for args, one for returns. It front-loads the key purpose, with no unnecessary words. Every sentence contributes useful information.

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 simplicity (one param, no output schema), the description adequately covers return type and effect. It mentions restoration within HubSpot, which is relevant. Minor gaps: no mention of idempotency or error cases, but scoring high due to overall clarity.

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 single parameter (contactId) is fully described in the schema with 100% coverage. The description repeats this information ('HubSpot contact record ID') without adding new meaning. Baseline score of 3 is appropriate since the schema already covers parameter semantics.

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 tool's purpose: 'Archive (soft-delete) a contact in HubSpot.' It specifies the resource (contact) and the action (archive/soft-delete), with additional context about moving to recycle bin. This distinguishes it from sibling delete tools for companies and deals.

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 implicitly distinguishes by entity type (contact vs company/deal) through the tool name and title. It clarifies that this is a soft-delete (archive) rather than a permanent removal, guiding the agent on when to use it. However, it lacks explicit when-not or alternative tool references.

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