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 but offers minimal behavioral insight. It states this is a read operation (non-destructive) but doesn't cover rate limits, permissions needed, error handling for invalid IDs, response format, or pagination behavior. For a batch tool with complex nested parameters, this leaves significant gaps in understanding how it behaves.

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 wasted words. It's front-loaded with the core purpose and uses clear terminology. Every word earns its place, making it easy to parse quickly while conveying the essential batch nature of the operation.

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 complexity (batch operation with nested object parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is inadequate. It doesn't explain the parameter structure, return values, error conditions, or behavioral constraints needed for effective use. For a tool with this level of parameter complexity, the description should provide much more 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 but fails to do so. It mentions 'multiple email records' but doesn't explain the 'inputs' parameter structure, what 'id' represents, what 'properties' and 'associations' arrays contain, or how to format requests. The description adds almost no semantic value beyond what's inferable from the parameter name 'inputs'.

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 ('Read') and resource ('multiple email records'), specifying it's a batch operation ('in a single request'). It distinguishes from individual read tools like 'emails_get' by emphasizing batch capability. However, it doesn't explicitly differentiate from other batch read tools like 'notes_batch_read' or 'products_batch_read' that follow similar patterns.

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. It doesn't mention when batch reading is preferable to individual reads ('emails_get'), when to use it versus listing/searching tools ('emails_list', 'emails_search'), or any prerequisites like authentication requirements. The context is implied but not explicit.

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