hubspot_batch_create_deals

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions max 100 deals but fails to describe error handling (partial failures), required permissions, rate limits, or return behavior. For a mutation tool, 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 a single, front-loaded sentence with no wasted words. It conveys the core function and constraint efficiently.

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 no output schema and no annotations, the description is too minimal. It lacks context on error handling, idempotency, or how to specify deal properties like pipeline or stage. Given the complexity of batch operations, more detail is needed.

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 input schema coverage is 100% with a description on the 'deals' parameter ('Array of deal properties to create'), which is sufficient but adds no extra meaning beyond the schema structure. The description does not elaborate on property details like format or required fields.

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 tool's purpose: creating multiple deals at once, with a max of 100. It uses a specific verb ('Create') and resource ('multiple deals'), and distinguishes from siblings like 'hubspot_create_deal' and 'hubspot_batch_update_deals'.

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 creation but does not explicitly state when to use this tool over alternatives. No guidance on when not to use or prerequisites. While the tool name and description hint at batch vs single, it lacks explicit context.

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