HubSpot MCP Server

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)') but lacks critical details such as permission requirements, whether the operation is reversible, rate limits, error handling for invalid IDs, or what happens to archived emails. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that front-loads the core action and resource. There is no wasted verbiage, and it directly communicates the tool's purpose without unnecessary elaboration, making it highly concise and well-structured.

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 (destructive batch operation), lack of annotations, no output schema, and 0% schema description coverage, the description is insufficient. It fails to address behavioral risks, parameter details, or expected outcomes, leaving significant gaps for an AI agent to understand and invoke the tool correctly in context.

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 0%, but the description does not add any parameter-specific information beyond implying 'emailIds' are needed. It doesn't explain the format of email IDs, constraints on array size, or validation rules. With one parameter and no schema descriptions, the baseline is 3 as the description minimally hints at the parameter's role without providing meaningful 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 action ('Archive (delete)') and resource ('multiple email records') with the operational context ('in a single request'). It distinguishes from the singular 'emails_archive' sibling by specifying batch processing, though it doesn't explicitly contrast with other batch operations like 'emails_batch_read' or 'emails_batch_update'.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing email IDs), compare it to the singular 'emails_archive', or specify scenarios where batch archiving is preferred over individual operations, leaving usage context unclear.

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