hubspot_crm_batch_read

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

The description discloses key behaviors: it reads records (implied read-only), handles per-record errors, and supports custom idProperty. It does not mention authentication, rate limits, or side effects, but since no annotations are provided, it carries the full burden and does well for a read operation.

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 concise at 5 sentences, front-loaded with the main purpose, and each sentence adds value (limit, object types, properties, idProperty, response structure). No redundancy or fluff.

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 read tool without an output schema, the description adequately covers inputs, limits, error handling, and response structure. It explains the core functionality and edge cases (custom idProperty) completely.

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 already provides clear descriptions for all 5 parameters (100% coverage). The description adds context by explaining how to use idProperty and that properties must be specified to control fields, but does not provide significant new meaning 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?

The description clearly states it reads up to 100 HubSpot CRM records by ID in a single request, applicable to all object types. The verb 'Read' and resource 'HubSpot CRM records' are specific, and the batch nature distinguishes it from sibling tools like hubspot_crm_get (single record) or hubspot_crm_search.

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 guidance on specifying properties and using idProperty for custom lookups, and mentions the 100-record limit. However, it does not explicitly state when to avoid this tool or contrast it with alternatives like search or list for filtering instead of IDs.

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