HubSpot MCP Server

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

With no annotations provided, the description carries full burden. It discloses pagination behavior ('Read a page of products', 'after is the paging cursor token') and mentions the response structure ('paging.next.after JSON property'). However, it doesn't address rate limits, authentication requirements, error conditions, or whether this is a safe read operation (though implied by 'Read').

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 appropriately sized with two sentences. The first sentence states the core purpose, and the second explains parameter usage and response behavior. There's no wasted text, though the second sentence is somewhat dense and could be structured more clearly.

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?

For a paginated list tool with 3 parameters, 0% schema coverage, and no output schema, the description provides adequate but incomplete context. It covers pagination mechanics and parameter purposes but lacks details about response format beyond cursor tokens, error handling, or performance characteristics. Given the complexity, more completeness would be beneficial.

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 adds meaningful context for all three parameters beyond the 0% schema coverage. It explains that 'properties' controls what is returned, and 'after' is a paging cursor token that appears in the response. While it doesn't detail 'limit' or provide format specifics, it gives functional understanding that compensates for the schema's lack of descriptions.

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 reads a page of products, specifying the verb ('Read') and resource ('products'). It distinguishes from siblings like products_create or products_update by focusing on listing rather than creating/modifying. However, it doesn't explicitly differentiate from products_search or products_read, which might have overlapping functionality.

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 like products_search or products_read. It mentions controlling returned properties via the 'properties' parameter but doesn't explain when this paginated list approach is preferred over search or direct read operations. 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.