post-crm-v3-objects-invoices-batch-upsert_upsert

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

With no annotations, the description must carry the behavioral burden. It discloses the create-or-update behavior and the unique-property matching logic, but omits important details like partial failure handling, idempotency, and response format. It adds some context beyond a bare tautology.

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 two-sentence description is front-loaded with the purpose and remains concise. However, the second sentence 'REQUIRES body parameter with request data' is slightly redundant and imprecise, since the schema calls the required field 'inputs' rather than 'body'.

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?

As a batch operation with no output schema, the description fails to explain return values, per-item error behavior, or the exact matching semantics for unique properties. Agents would need to make assumptions about how partial successes or failures are reported, which is a significant gap.

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 coverage is 100% with descriptive text for all fields, so the baseline is 3. The description adds little beyond pointing to the inputSchema; the 'unique property values' hint aligns with the idProperty field but does not enhance schema semantics.

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 or update a batch of invoices') and the mechanism ('by unique property values'), which distinguishes it from batch-create and batch-update siblings that operate purely on IDs. The verb, resource, and condition are all specific.

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 phrase 'by unique property values' implies when to use this tool (when you have unique properties rather than IDs), but it does not explicitly state when not to use it or provide alternatives like batch-create or batch-update. Usage context is only implied.

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