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 for behavioral disclosure but provides almost none. It states this is a creation operation but doesn't mention permissions required, whether this is a write operation (implied but not stated), rate limits, error handling, what happens on partial failures, or any other behavioral characteristics. The single sentence offers no transparency beyond the basic action.

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 maximally concise with a single sentence that communicates the core functionality. There's no wasted language, repetition, or unnecessary elaboration. It's front-loaded with the essential information, 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 creation tool with complex nested parameters (0% schema coverage), no annotations, and no output schema, the description is completely inadequate. It doesn't explain what data notes contain, how associations work, what permissions are needed, what the response looks like, or any error conditions. The single sentence fails to provide the context needed for effective tool 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?

With 0% schema description coverage and 1 parameter (a complex nested array), the description provides zero information about parameters. It doesn't mention the 'inputs' parameter at all, doesn't explain the structure of note objects, required fields like 'hs_note_body', or the associations system. 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 clearly states the action ('Create multiple notes') and resource ('notes'), making the purpose immediately understandable. It distinguishes from the singular 'notes_create' sibling by specifying batch operations, though it doesn't explicitly contrast with other batch operations like 'notes_batch_update' or 'notes_batch_archive'.

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. It doesn't mention when batch creation is preferable to individual creation, doesn't reference sibling tools like 'notes_create' or 'notes_batch_update', and offers no context about prerequisites, limitations, or appropriate use cases.

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