HubSpot MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a creation tool, implying mutation, but doesn't cover critical aspects like required permissions, rate limits, error handling, or whether it's idempotent. The description is too minimal to inform the agent adequately about behavioral traits.

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, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core action, making it easy to parse quickly.

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 of the input schema (deeply nested with many properties), lack of annotations, and no output schema, the description is severely incomplete. It fails to address parameter usage, behavioral expectations, or output format, leaving the agent with insufficient information to use the tool effectively.

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 description provides no information about parameters. With schema description coverage at 0% and a complex nested parameter structure (e.g., 'inputs' array with 'properties' and 'associations'), the agent lacks essential context on how to structure the input, what fields are mandatory, or the meaning of nested objects like 'associations'. This significantly hampers usability.

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 leads') and resource ('leads'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'crm_batch_create_companies' or 'crm_batch_create_contacts', which have similar batch creation patterns but for different resources.

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. For example, it doesn't mention when to prefer batch creation over single creation ('crm_create_lead') or how it relates to other batch tools like 'crm_batch_update_leads'. The description lacks context about prerequisites or typical use cases.

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