HubSpot MCP Server

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

No annotations are provided, so the description carries full burden. It states 'Create' implying mutation but doesn't disclose behavioral traits like permissions needed, rate limits, whether it's idempotent, error handling for partial failures, or response format. For a batch mutation tool with zero annotation coverage, this is a significant gap.

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 front-loaded with the core purpose and appropriately sized for the tool's complexity.

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 a batch mutation tool with 2 parameters (including complex nested objects), 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It lacks details on usage, behavior, parameters, and expected outcomes, leaving significant gaps for 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?

Schema description coverage is 0%, so the description must compensate. It mentions 'multiple CRM objects' hinting at an array input but doesn't explain the 'objectType' enum or 'inputs' structure with 'properties' and 'associations'. The description adds minimal value beyond what's inferable from 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 the action ('Create multiple') and resource ('CRM objects'), specifying it's a batch operation ('in a single request'). It distinguishes from single-create tools like 'crm_create_object' but doesn't explicitly differentiate from other batch create tools like 'crm_batch_create_companies' or 'crm_batch_create_contacts'.

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 on when to use this tool versus alternatives like single-object creation tools or type-specific batch tools (e.g., 'crm_batch_create_companies'). The description implies batch creation but doesn't specify scenarios, prerequisites, or exclusions.

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