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 but only states it's a read operation. It doesn't disclose behavioral traits like rate limits, authentication requirements, pagination, error handling for partial failures, or what happens with invalid IDs. This leaves significant gaps 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 a single, clear sentence with zero wasted words. It's appropriately sized for a simple tool description and front-loads the essential information.

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 batch read tool with 1 parameter (but complex nested structure), 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain the input structure, output format, error behavior, or performance characteristics needed for 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 but adds nothing about parameters. It doesn't explain what 'inputs' contains, the purpose of 'id', 'properties', or 'associations', or how to structure the array. This leaves all parameter semantics undocumented.

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 action ('Read multiple tasks') and scope ('in a single request'), which distinguishes it from single-task read operations. However, it doesn't explicitly differentiate from other batch read tools for different resources (like calls_batch_read or notes_batch_read), keeping it at a 4 rather than a 5.

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_get (for single tasks) or tasks_list (for listing with filters). There's no mention of performance trade-offs, prerequisites, or error handling for batch operations.

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