hubspot_crm_batch_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals the 100-record limit, per-record error returns, optional associations, and the hs_timestamp requirement for engagements. However, it does not specify whether the batch operation is fully atomic or handles partial failures, which would be useful for a mutation tool. This gap prevents a 5.

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 four sentences, each earning its place: 1) core purpose and batch size, 2) applicability and input structure, 3) special requirement for engagements, 4) return behavior. No fluff, well-front-loaded.

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 tool's complexity (batch creation with optional associations), no output schema, and no annotations, the description covers the key aspects: limit, input format, special requirement, and return type. It could be more explicit about output structure (e.g., whether IDs are returned) but is still quite complete for a batch creation tool.

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 100%, so the baseline is 3. The description adds value beyond the schema by highlighting the batch limit, the engagement timestamp requirement, and the atomic creation of associations. This additional context justifies a 4.

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 creates up to 100 HubSpot CRM records in a single request, applicable to all object types. It distinguishes from siblings like hubspot_crm_create (single record) and other batch operations (read, update, upsert, archive) by specifying batch creation and the 100-record limit.

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 provides usage context: it's for creating records in bulk, applies to all object types, and notes a special requirement for engagements (hs_timestamp). While it doesn't explicitly contrast with alternatives, the sibling tools list and the description's focus on batch creation make the usage clear. A score of 4 is appropriate due to lack of explicit when-not-to-use guidance.

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