HubSpot MCP Server

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

No annotations are provided, so the description must fully disclose behavioral traits. However, the description incorrectly claims a create operation, which contradicts the likely read behavior implied by the name and schema (which includes parameters like 'objectIds' for reading specific objects). This misrepresentation fails to provide any accurate 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 a single sentence, which is concise, but it is under-specified and misleading. While it avoids unnecessary length, it fails to provide meaningful information, making it ineffective rather than efficiently informative.

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 5 parameters with 0% schema coverage, no annotations, no output schema, and a misleading description, the description is completely inadequate. It does not clarify the tool's purpose, usage, behavior, or parameters, leaving the agent with insufficient information to use the tool correctly.

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 5 parameters are documented in the schema. The description does not mention any parameters or their purposes, failing to compensate for the lack of schema documentation. Parameters like 'objectType', 'objectIds', and 'properties' remain unexplained.

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 multiple CRM objects in a single request' is misleading and contradicts the tool's name 'crm_batch_read_objects' and input schema. The name suggests a read operation, while the description incorrectly states a create operation. This creates confusion about the tool's actual purpose.

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?

The description provides no guidance on when to use this tool versus alternatives. With numerous sibling tools like crm_batch_read, crm_get_object, crm_list_objects, and crm_search_objects, there is no indication of how this tool differs or when it should be preferred over other read operations.

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