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 but fails completely. It doesn't indicate whether this is a read-only operation, whether it has side effects, what authentication might be required, or any rate limits. For a search tool with 6 parameters and complex filtering capabilities, this lack of behavioral information is a significant gap.

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?

While technically concise with just two words, this represents under-specification rather than effective conciseness. The description is front-loaded but provides so little information that it fails to serve its purpose. Every word should earn its place, but here the words don't provide enough value to justify their inclusion.

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 (6 parameters with nested objects, no output schema, no annotations), the description is completely inadequate. It doesn't explain the tool's purpose beyond the name, provides no parameter guidance, offers no behavioral context, and gives no indication of what the search returns. For a tool with this level of complexity, the description fails to provide even basic contextual information.

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?

With 0% schema description coverage for all 6 parameters, the description provides zero information about what the parameters mean or how to use them. The schema shows complex filtering capabilities (filterGroups with operators, sorts, properties, etc.), but the description doesn't even hint at these capabilities. The description fails to compensate for the complete lack of schema documentation.

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 'Search products' is a tautology that merely restates the tool name without adding specificity. It doesn't clarify what kind of search this performs (full-text, filtered, etc.) or what resource scope it covers. While it does include the verb 'search' and resource 'products', it lacks the differentiation needed to distinguish it from other product-related tools like products_list or products_read.

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 absolutely no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, context for usage, or comparison to sibling tools like products_list. The agent receives no help in determining when this search tool is appropriate versus other product-related operations.

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