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. It describes a read operation (implied safe/non-destructive) but lacks details on permissions, rate limits, error handling, or response format. The mention of retrieving records by custom unique values adds some context, but overall behavioral traits are under-specified for a batch operation.

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 concise (two sentences) and front-loaded with the main purpose. However, the second sentence is somewhat redundant with the first and could be more efficiently integrated. While not wasteful, it lacks the precision of top-tier descriptions.

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 (batch operation with 4 parameters, 3 required), 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain parameter interactions, expected output, error conditions, or how this differs from similar sibling tools, leaving significant gaps for an AI 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%, so the description must compensate for all 4 parameters. It only mentions 'idProperty' for custom unique values, leaving 'propertiesWithHistory', 'productIds', and 'properties' unexplained. This provides minimal semantic value beyond the bare schema, failing to clarify what these arrays contain 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 clearly states the tool's purpose: reading a batch of products by internal ID or unique property values. It specifies the verb ('Read'), resource ('products'), and scope ('batch'), but doesn't explicitly differentiate from sibling tools like 'products_read' or 'products_list' beyond mentioning batch retrieval.

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 minimal usage guidance, mentioning the 'idProperty' parameter for custom unique values but not explaining when to use this tool versus alternatives like 'products_read' (single product) or 'products_list' (list with filters). No explicit when/when-not scenarios or prerequisites are provided.

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