HubSpot MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails completely. It doesn't mention that this is a write operation requiring permissions, doesn't describe what happens upon creation (e.g., returns a meeting ID), doesn't warn about required fields, and provides no information about rate limits, error conditions, or system behavior.

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 three words. While this represents severe under-specification, from a pure conciseness perspective it's front-loaded with zero wasted words and no structural issues.

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 (2 parameters with nested objects, no output schema, no annotations), the description is completely inadequate. It doesn't explain what the tool returns, what permissions are needed, how to structure the complex input, or provide any context about the meeting creation process in the broader system.

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?

The schema description coverage is 0%, meaning none of the parameters are documented in the schema. The description adds no information about the 2 top-level parameters ('properties' and 'associations') or their complex nested structures. For a tool with 2 parameters and rich nested objects, this leaves the agent completely in the dark about what data to provide.

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 meeting' is essentially a tautology that restates the tool name 'meetings_create' without adding meaningful specificity. It doesn't distinguish this tool from sibling tools like 'meetings_batch_create' or 'calls_create', nor does it clarify what kind of meeting is being created or in what context.

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?

There is no guidance on when to use this tool versus alternatives. The description provides no context about prerequisites, when this tool is appropriate versus batch operations, or what distinguishes it from other creation tools in the sibling list like 'calls_create' or 'tasks_create'.

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