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. While 'Update' implies mutation, the description doesn't disclose important behavioral traits like whether this requires specific permissions, if updates are atomic or partial, what happens on partial failures, or rate limiting considerations. For a batch mutation tool with zero annotation coverage, this is insufficient.

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, efficient sentence with zero wasted words. It's appropriately sized and front-loaded with the core functionality, though this conciseness comes at the cost of completeness.

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 mutation tool with complex nested parameters (1 parameter with deep nesting), 0% schema description coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't address error handling, response format, permissions, or provide any context about the task properties that can be updated.

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 and a complex nested parameter structure (array of objects with id and properties), the description adds no parameter information beyond the tool name. It doesn't explain what 'inputs' should contain, the required fields, or the meaning of the various hs_task_* properties documented in the schema.

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 ('Update multiple tasks') and the scope ('in a single request'), which provides a specific verb+resource combination. However, it doesn't explicitly distinguish this batch operation from the individual 'tasks_update' sibling tool, which would be helpful for 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 batch update tool versus the individual 'tasks_update' tool, nor does it mention prerequisites, error handling, or rate limits. Without any usage context, the agent must infer when batch operations are appropriate.

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