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. The description claims a 'Create' operation which contradicts the tool name 'read_objects' - this inconsistency creates fundamental confusion about whether this is a read or write operation. No behavioral traits like permissions needed, rate limits, or response format are disclosed.

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 this conciseness comes at the cost of being misleading and incomplete. While it's front-loaded, the single sentence doesn't earn its place by providing accurate or helpful information.

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 tool with 5 parameters, 0% schema coverage, no annotations, no output schema, and numerous sibling alternatives, the description is completely inadequate. It provides contradictory information about the tool's purpose and offers no guidance on usage, parameters, or behavior - leaving 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?

With 0% schema description coverage and 5 parameters, the description provides no information about any parameters. It doesn't explain what 'objectType' enum values mean, what 'propertiesWithHistory' does, how 'idProperty' is used, or the purpose of 'objectIds' and 'properties' arrays. The description fails completely to compensate for the schema coverage gap.

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 essentially restates the tool name 'crm_batch_read_objects' with a contradictory verb ('Create' vs 'read'). This creates confusion rather than clarifying purpose. It fails to distinguish from sibling tools like crm_batch_create_objects or crm_batch_update_objects.

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 about when to use this tool versus alternatives. With numerous sibling tools for CRM operations (batch create, batch update, individual reads, searches), the description offers no context about appropriate use cases, prerequisites, or distinctions from similar tools.

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