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 write operation ('Create') but the tool name suggests reading, creating fundamental confusion about whether this is a read or write operation. No information about permissions, rate limits, side effects, or response format.

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's technically concise, but it's under-specified rather than efficiently informative. While it's front-loaded, it fails to provide necessary context for a tool with 5 parameters and no annotations.

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?

Completely inadequate for a 5-parameter tool with no annotations and no output schema. The description contradicts the tool name, provides no parameter information, and offers no behavioral context. This leaves the agent with insufficient information to use the tool correctly.

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 the description must compensate for 5 undocumented parameters. The description provides no information about any parameters - it doesn't mention objectType, objectIds, properties, propertiesWithHistory, or idProperty. This leaves all parameters completely unexplained.

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 states 'Create multiple CRM objects in a single request' which is a tautology that restates the tool name 'crm_batch_read_objects' - the name suggests reading while the description suggests creating, creating confusion. It doesn't specify what type of objects or distinguish from sibling tools like crm_batch_create_objects or crm_batch_read.

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 on when to use this tool versus alternatives like crm_batch_create_objects, crm_batch_read, or crm_get_object. The description contradicts the tool name (read vs create), providing misleading usage information.

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