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. 'Create' implies a write/mutation operation, but the description doesn't disclose behavioral traits like required permissions, whether this is idempotent, what happens on failure, rate limits, or what the response contains. For a creation tool with complex nested parameters, 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 extremely concise at just 5 words. It's front-loaded with the core action and resource. There's zero wasted language, though this conciseness comes at the cost of completeness for such a complex tool.

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 (3 nested parameters, no output schema, no annotations), the description is inadequate. It doesn't explain what an 'engagement' is in this context, how it differs from other objects, what the creation response looks like, or any behavioral expectations. For a creation tool with such rich input structure, more context is needed.

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 schema provides no parameter descriptions. The description mentions 'with details' which vaguely hints at the three complex nested parameters (engagement, associations, metadata), but adds almost no semantic meaning about what these parameters represent, their relationships, or how they should be used. It doesn't compensate for the complete lack of schema documentation.

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 'Create a new engagement with details' states the basic action (create) and resource (engagement), but is vague about what 'with details' means. It doesn't distinguish this tool from sibling engagement tools like 'engagement_details_update' or 'crm_create_object' that might also handle engagements. The purpose is understandable but lacks specificity.

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. With many sibling tools including 'engagement_details_update', 'crm_create_object', and various batch/create tools, the description offers no context about appropriate use cases, prerequisites, or distinctions from similar tools.

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