hubspot_crm_batch_upsert

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

Describes create/update behavior, input requirements, and idProperty uniqueness constraint. No annotations provided, so description does the heavy lifting; however, lacks details on partial failures, rate limits, or atomicity.

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?

Concise and front-loaded. Each sentence provides essential information without redundancy.

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?

Covers primary aspects: action, required fields, limit, and special notes (unique property, timestamp). Missing error handling or response details, but overall adequate for a batch upsert 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 coverage is 100%, and description adds extra context: idProperty must be unique, properties are string-only, and for engagements hs_timestamp is required. Adds value beyond 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 'Upsert up to 100 HubSpot CRM records' with the create/update logic, specifying the resource, action, and limit. Distinct from siblings like batch_create and batch_update.

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?

Specifies required inputs (idProperty, id, properties) and the 100-record limit. Notes that idProperty must be unique. Does not explicitly contrast with batch_create or batch_update, but the upselt nature is implied.

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