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 an update operation. It lacks critical behavioral details: whether this is atomic/partial, permission requirements, rate limits, error handling for invalid inputs, or what happens to existing note properties not mentioned. For a 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 front-loaded with the core action and scope, making it easy to parse quickly.

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 1 parameter (complex nested array), 0% schema description coverage, no annotations, and no output schema, the description is incomplete. It misses essential context like input format, behavioral constraints, and expected outcomes, leaving significant gaps for an AI agent to use it 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%, so the description must compensate but adds no parameter information. It doesn't explain the 'inputs' array structure, required fields like 'id' and 'properties', or the specific properties (hs_note_body, hs_timestamp, hubspot_owner_id) that can be updated. The baseline would be 3 if schema coverage were high, but here it's low with no compensation.

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 verb ('Update') and resource ('multiple notes'), and specifies the scope ('in a single request'). It distinguishes from individual update operations but doesn't explicitly differentiate from sibling batch tools for other resources like calls or emails, which would require a perfect 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?

No guidance is provided on when to use this tool versus alternatives like 'notes_update' (for single updates) or other batch operations. The description implies batch efficiency but doesn't state prerequisites, limitations, or trade-offs compared to single updates.

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