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 states this is a read operation, implying it's non-destructive, but doesn't mention any behavioral traits such as rate limits, authentication needs, error handling, or what happens if IDs are invalid. The description lacks details on return format, pagination, or performance characteristics.

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 with two sentences that directly address the tool's functionality. It's front-loaded with the main purpose and avoids unnecessary fluff. However, the second sentence is slightly redundant with the first, and it could be more structured by explicitly listing parameter roles.

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 (4 parameters, 3 required), 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain what the tool returns, how to handle the array parameters, or the interaction between productIds and idProperty. For a batch read tool with multiple inputs, more context is needed to guide effective use.

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 undocumented parameters. It only explains the idProperty parameter ('to retrieve records by a custom unique value property'), leaving productIds, properties, and propertiesWithHistory unexplained. This adds minimal value beyond the schema, failing to clarify the purpose or usage of most parameters.

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 using internal IDs or unique property values. It specifies the verb ('Read'), resource ('products'), and scope ('batch'), distinguishing it from sibling tools like products_read (singular) and products_list (list all). However, it doesn't explicitly differentiate from products_search, which might also retrieve products by criteria.

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 implies usage by mentioning two retrieval methods (by internal ID or unique property values via idProperty), but it doesn't provide explicit guidance on when to use this tool versus alternatives like products_read (single product), products_list (list all), or products_search (search by criteria). No exclusions or prerequisites are mentioned.

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