HubSpot MCP Server

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Search tasks with specific filters' doesn't reveal whether this is read-only, paginated, rate-limited, requires authentication, or what the return format looks like. It's completely inadequate for a search tool with complex filtering capabilities.

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 extremely concise (4 words), but this brevity comes at the cost of being under-specified rather than efficient. While front-loaded, it doesn't provide enough information to be genuinely helpful. It's not verbose, but it's also not adequately 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?

This is a complex search tool with 5 parameters (including nested filtering logic), no annotations, no output schema, and 0% schema description coverage. The description is completely inadequate for this context - it doesn't explain the filtering system, pagination, sorting, or what properties can be searched. The agent would struggle to use this 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?

Schema description coverage is 0%, meaning none of the 5 parameters are documented in the schema. The description mentions 'specific filters' which hints at the 'filterGroups' parameter but doesn't explain any of the other parameters (properties, limit, after, sorts) or provide syntax/format guidance. It 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 tasks with specific filters' states the basic action (search) and resource (tasks), but it's vague about what 'specific filters' means and doesn't distinguish this tool from sibling tools like 'tasks_list' or 'tasks_get'. It restates the name/title concept without adding meaningful differentiation.

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 'tasks_list' or 'tasks_get'. There's no mention of prerequisites, appropriate contexts, or exclusions. The agent must guess based on the name alone.

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