hubspot_batch_update_deals

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

The description discloses the mutational nature ('Update') and batch limit (max 100), which are key behavioral traits. But with no annotations, it does not cover potential partial failures, idempotency, or whether updates are partial/full replacements. This is adequate but not thorough.

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 sentence that conveys the core functionality and a critical constraint. Every word is necessary; there is no wasted text. Excellent conciseness.

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 no output schema and no annotations, the description should provide more context, such as error handling behavior, whether updates are atomic, and whether unspecified properties are preserved. The minimal description leaves important gaps for an AI agent.

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?

The description adds the 'max 100' constraint and the 'multiple deals' aspect, but these are already present in the input schema (maxItems: 100, description on deals array). The schema covers 100% of top-level parameters, so the description adds minimal value beyond the schema. Baseline 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 clearly states the core action ('Update multiple deals at once') and specifies a key constraint (max 100). It effectively distinguishes the tool from the singular update tool (hubspot_update_deal) and the batch creation tool (hubspot_batch_create_deals) in the sibling list.

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 bulk updates and notes the batch limit, providing clear context. However, it lacks explicit guidance on when not to use it (e.g., for single updates use hubspot_update_deal) and does not refer to alternative tools.

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