Archive multiple HubSpot tasks simultaneously by providing task IDs in a single batch request to clean up completed items.
Archive (delete) multiple tasks in a single request
| Name | Required | Description | Default |
|---|---|---|---|
| taskIds | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden but only states the action ('archive (delete)'). It lacks critical behavioral details like whether deletion is permanent/reversible, required permissions, rate limits, error handling for partial failures, or confirmation prompts. This is inadequate 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 with no 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 destructive batch tool with no annotations and no output schema, the description is insufficient. It doesn't address critical context like side effects, success/error responses, or how it differs from single-task deletion. More detail is needed given the complexity and risk.
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's purpose ('multiple tasks'). However, it doesn't specify format constraints (e.g., ID requirements, array size limits) or provide examples. Baseline 3 is appropriate as it adds minimal value beyond the bare 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 verb ('archive (delete)') and resource ('multiple tasks'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling 'tasks_archive' (single vs. batch), which prevents a perfect score.
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 'tasks_archive' (single task) or other batch operations. The description mentions 'multiple tasks' but doesn't clarify thresholds or prerequisites for batch usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.