hubspot_crm_archive

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

The description fully discloses behavioral traits: it's a soft-delete (not permanent), records can be retrieved with archived=true, returns HTTP 204 on success, and provides alternative for permanent deletion. Since no annotations are provided, the description carries the full burden and excels.

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?

Three sentences: first defines action, second explains behavior and retrieval, third gives response and alternative. Front-loaded with purpose, no wasted words.

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 2-parameter tool with no output schema, the description covers all essential aspects: action, behavior (soft-delete vs permanent), retrieval method, response format, and alternative. Complete for agent decision-making.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds that it applies to 'all object types,' which is already implied by the enum in the schema. No significant additional semantic value beyond the schema.

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 'Archive (soft-delete) a HubSpot CRM record', identifying the verb (archive/soft-delete) and resource (CRM record). It distinguishes from siblings like batch_archive by implying single-record operation, and contrasts with permanent deletion.

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 mentions it applies to all object types and provides an alternative for permanent deletion ('To permanently delete, use the HubSpot UI or the GDPR delete endpoint'). It implicitly guides when to use this tool for reversible soft-delete, but does not explicitly differentiate from batch archive or other sibling tools beyond name.

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