HubSpot MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It indicates a destructive action ('Archive (delete)'), implying mutation and potential irreversibility, but fails to mention critical details like permissions required, confirmation steps, rate limits, or what happens to associated data. This leaves significant gaps for a tool that performs deletion.

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 with a single, front-loaded sentence that directly states the action and resource without any unnecessary words. It efficiently communicates the core purpose, making it easy to parse and understand quickly.

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 complexity as a destructive operation with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks essential context such as behavioral implications, error handling, return values, and differentiation from siblings, making it inadequate for safe and effective use by an AI agent.

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 description does not add any parameter details beyond the input schema, which has 0% description coverage and only specifies 'callId' as a required string. Since schema coverage is low, the description does not compensate by explaining the parameter's meaning, format, or examples, but the single parameter is straightforward, so it meets the baseline for minimal viability.

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 verb ('Archive (delete)') and resource ('a call record'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'calls_batch_archive' or 'calls_update', which might handle multiple calls or updates instead of single deletion, leaving room for slight ambiguity in sibling distinction.

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 provides no guidance on when to use this tool versus alternatives, such as 'calls_batch_archive' for multiple calls or 'calls_update' for modifications. It lacks context on prerequisites, exclusions, or specific scenarios, offering only a basic action statement without usage instructions.

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