hubspot_batch_create_contacts

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

With no annotations, the description bears full responsibility for behavioral disclosure. It mentions max 100 contacts but omits details on error behavior, idempotency, required permissions, or what happens on duplicate emails. This lack of transparency could lead to misinvocation.

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 immediately conveys the core action and constraint. Every word is necessary and front-loaded, making it efficient for an AI agent to parse.

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 no output schema and no annotations, the description lacks crucial context such as what the tool returns (e.g., created contact IDs), how partial failures are handled, and whether the tool is idempotent. For a batch operation, this is insufficient for safe and effective use.

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 covers 100% of parameters, with a description for the 'contacts' array. The description adds the 'max 100' constraint which is already present in the schema's maxItems. No additional semantic guidance is provided for the individual fields (email, phone, etc.), so the description offers minimal added value beyond the 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?

Description clearly states the tool creates multiple contacts at once with a max limit of 100. The name 'batch_create_contacts' reinforces the batch operation, distinguishing it from single-contact creation tools like hubspot_create_contact.

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?

Description does not specify when to use this tool versus alternatives like hubspot_create_contact for single contacts. No guidance on error handling, partial failures, or prerequisites is provided. The batch nature is implied but not explicitly contrasted with other tools.

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