post-crm-v3-objects-invoices-batch-create_create

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

With no annotations provided, the description must disclose behavioral traits. It only says 'Create a batch of invoices', which implies mutation, but does not mention response format, failure behavior, idempotency, or limits. Additionally, the example uses 'body' while the input schema requires 'inputs', creating confusion about the expected parameter structure.

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 compact, with the purpose front-loaded and an example that aids understanding. However, the example is somewhat verbose and the 'body' wrapper adds unnecessary complexity, so it is not perfectly streamlined.

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 create operation with no output schema and no annotations, the description should provide more context about return values, batch size limits, partial failure handling, or required invoice-specific fields. It only offers a generic example, leaving significant gaps for an agent to invoke 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 100%, so the baseline is 3. The example provides a concrete shape for the inputs array, which adds value, but it may be misleading by wrapping in a 'body' object that is not present in the schema. It does not clarify nested parameters like associations or objectWriteTraceId beyond their schema definitions.

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 'Create a batch of invoices', identifying the specific verb (create), resource (invoices), and scope (batch). This distinguishes it from sibling tools like batch update, upsert, or archive operations, especially given the 'invoices' object type in the tool name.

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 an example and a requirement that a body parameter is needed, but does not explicitly state when to use this tool over alternatives like batch update or upsert. Usage is implied by the verb 'create' and the batch context, but no exclusions or alternative comparisons are given.

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