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. It states the tool archives (deletes) multiple call records, indicating a destructive mutation, but lacks details on permissions, reversibility, error handling, or rate limits. This is a significant gap for a destructive 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, efficient sentence that front-loads the key action and scope. There is no wasted verbiage, making it highly concise and well-structured for quick understanding.

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 destructive batch tool with no annotations, 0% schema description coverage, and no output schema, the description is inadequate. It lacks critical behavioral details like safety warnings, response format, or error conditions, leaving the agent under-informed for proper invocation.

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%, but the description implies the parameter 'callIds' is an array of call records to archive. However, it doesn't specify format, constraints, or maximum batch size. With one parameter and no schema descriptions, the description adds minimal value beyond the schema's structure.

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 ('archive (delete)') and resource ('multiple call records') with the scope 'in a single request.' It distinguishes from the singular 'calls_archive' sibling by specifying batch operation, though it doesn't explicitly contrast with other batch operations like 'calls_batch_create' or 'calls_batch_update.'

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 explicit guidance on when to use this tool versus alternatives like 'calls_archive' for single deletions or other batch operations. The description implies batch deletion but doesn't mention prerequisites, constraints, or comparative use cases with sibling tools.

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