hubspot_batch_update_contacts

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry behavioral details. It discloses the max batch size (100) but does not mention important aspects such as partial failure behavior, idempotency, rate limits, or authentication requirements. For a batch write operation, 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 extremely concise at 5 words, which is efficient but at the expense of missing important contextual information. It is front-loaded with the key action and constraint, yet the brevity leaves gaps in 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?

Given the complexity of a batch update operation and the absence of annotations and output schema, the description is incomplete. It lacks details on error handling, success/failure reporting, and exactly which properties can be updated (schema covers this, but description should reinforce). More context is needed for an agent to use this tool reliably.

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 coverage is 100%: every parameter has a description. The description adds 'max 100' which is already present in the schema as maxItems. Thus, the description provides minimal additional meaning beyond the schema. The baseline of 3 is appropriate.

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 'Update multiple contacts at once (max 100)' clearly states the action (update), resource (contacts), and a key constraint (batch with maximum of 100). This distinguishes it from sibling tools like hubspot_update_contact (single) and hubspot_batch_create_contacts (create).

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 implies usage for batch updates but does not explicitly state when to use this tool over alternatives, such as hubspot_update_contact for single updates, or any prerequisites like having contact IDs. No 'when not to use' guidance is provided.

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