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 for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't mention permissions required, whether associations are reversible, rate limits, error handling for partial failures, or what happens on success. For a batch creation tool with complex nested parameters, this is a significant gap in behavioral context.

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 at just 7 words, with zero wasted language. It's front-loaded with the core action ('Create multiple associations') and adds necessary scope ('in a single request'). Every word earns its place, making it efficient despite its informational shortcomings.

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 (3 parameters with nested objects, 0% schema description coverage, no annotations, no output schema), the description is inadequate. A batch creation tool for CRM associations needs more context about what associations are, how they work, success/failure behavior, and parameter meanings. The current description leaves too many gaps for effective tool selection and invocation.

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 adds no parameter information. The three parameters (fromObjectType, toObjectType, inputs) and their complex nested structure (including arrays of objects with specific required fields) are completely undocumented in the description. The agent must rely solely on the schema without any semantic explanation of what these parameters represent.

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 states the action ('create multiple associations') and scope ('in a single request'), which is clear but basic. It doesn't specify what 'associations' are in this CRM context or distinguish this from sibling tools like 'crm_create_association' (singular) or 'crm_batch_create_objects' (different resource type). The purpose is understandable but lacks specificity about the resource being manipulated.

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 when batch creation is preferable to single creation (crm_create_association), what prerequisites exist, or how it differs from other batch operations like crm_batch_create_objects. The agent must infer usage from the name alone.

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