post-crm-v4-objects-objtype-batch-create_create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Create a batch of objects' and shows an example; it does not mention batch size limits, partial failure behavior, validation rules, authentication requirements, or whether the operation is destructive/irreversible.

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 extremely concise: two short sentences plus an inline example. It front-loads the core purpose and gives a concrete usage pattern without extraneous details.

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 creation tool with moderate complexity and no output schema, the description provides a minimal viable invocation example but lacks important contextual details such as maximum batch size, error handling, and response format. The schema covers structure, but the description does not enrich the context further.

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?

Input schema documentation coverage is 100%, so the baseline is 3. The description adds a useful JSON example showing the nested structure for 'properties', but it introduces a 'body' wrapper not present in the schema (which expects 'inputs' directly), creating slight ambiguity. The example clarifies the shape but does not significantly extend beyond schema descriptions.

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 the action ('Create a batch of objects') and provides a concrete example, making the tool's primary function immediately understandable. However, it does not differentiate this create operation from sibling batch operations like update or upsert, relying on the tool name for that distinction.

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 mentions a required body parameter and provides an example, but gives no guidance on when to use this tool versus the many alternatives (e.g., batch-upsert, batch-update). There are no explicit exclusions or conditions for appropriate use.

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