HubSpot MCP Server

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

With no annotations provided, the description carries full burden. It states this is an update operation (implies mutation) but doesn't disclose behavioral traits like required permissions, whether changes are reversible, rate limits, error handling for partial failures, or what the response looks like. For a batch mutation tool with zero annotation coverage, this is inadequate.

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 with zero waste. It's appropriately sized for a tool with a clear name, though the brevity comes at the cost of completeness. Every word earns its place.

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 batch mutation tool with 1 parameter (complex nested array), 0% schema description coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't explain the input structure, behavioral implications, error handling, or what constitutes a successful update. The agent would struggle to use this correctly without additional 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%, so the description must compensate. It mentions 'multiple email records' which hints at an array structure, but provides no details about parameter format, required fields, or the meaning of properties like hs_email_status or hubspot_owner_id. The single sentence doesn't add meaningful semantic context beyond what's implied by the tool name.

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 ('update') and resource ('multiple email records'), and specifies it's a batch operation ('in a single request'). It distinguishes from non-batch email tools but doesn't explicitly differentiate from other batch operations like emails_batch_create or emails_batch_archive.

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 like emails_update (single update) or emails_batch_create (batch creation). It mentions 'multiple email records' which implies batch scenarios, but offers no explicit when/when-not guidance or prerequisites.

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