crm_batch_read_objects

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

No annotations are provided, so the description carries full burden. It claims a 'Create' operation, which implies mutation, but the tool name suggests reading. This inconsistency fails to disclose behavioral traits like whether it's read-only, requires permissions, handles errors, or returns data, making it inadequate for a tool with 5 parameters.

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, efficient sentence with no wasted words. It's front-loaded and appropriately sized for its content, though the brevity contributes to its inadequacy in other dimensions.

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 5 parameters with 0% schema coverage, no annotations, no output schema, and a misleading description, the tool definition is highly incomplete. It lacks essential details on behavior, parameters, and usage, making it insufficient for effective agent operation.

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 0%, so parameters are undocumented in the schema. The description adds no information about any parameters (e.g., objectType, objectIds, properties), failing to compensate for the coverage gap. This leaves the agent with no semantic understanding of inputs.

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 'Create multiple CRM objects in a single request' states a verb ('Create') and resource ('CRM objects'), but it's misleading given the tool name 'crm_batch_read_objects' and sibling tools like 'crm_batch_create_objects' that suggest this is a read operation, not a create operation. This creates confusion rather than clarity.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling CRM tools (e.g., crm_batch_create_objects, crm_batch_update_objects, crm_get_object, crm_list_objects), the description offers no context on use cases, prerequisites, or distinctions, leaving the agent to guess.

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