HubSpot MCP

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action 'create' without addressing permissions, side effects, error conditions, or response format. For a mutation tool with 11 parameters, this lack of transparency is inadequate and could lead to misuse.

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, direct sentence with no wasted words. It is front-loaded and efficiently communicates the core action, though this brevity comes at the cost of completeness. Every word earns its place in stating the tool's basic purpose.

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 (11 parameters, mutation operation, no annotations, no output schema), the description is severely incomplete. It does not address parameter meanings, behavioral traits, usage context, or output expectations. This is inadequate for a tool of this nature, leaving critical gaps for the 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%, meaning none of the 11 parameters are documented in the schema. The description adds no information about parameters, failing to compensate for this gap. It does not explain what fields like 'fieldType', 'options', or 'hasUniqueValue' mean or how they interact.

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 contact property' restates the tool name with minimal elaboration. It specifies the verb 'create' and resource 'contact property', but lacks detail on what a contact property is or how it differs from similar tools like crm_create_company_property or crm_create_lead_property. This is borderline tautological, scoring above 1 only because it includes the resource type.

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 does not mention prerequisites, context, or comparisons to sibling tools like crm_create_company_property or crm_get_contact_properties. This leaves the agent without direction on appropriate usage scenarios.

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