post-crm-v3-objects-line_items-batch-upsert_upsert

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

With no annotations, the description carries the full burden. It discloses that the tool creates or updates in batch, but does not mention important behavioral aspects such as idempotency, partial failure behavior, required permissions, rate limits, or what happens with conflicting unique property values.

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 short and front-loaded with the core purpose. The second sentence about checking the schema is somewhat redundant but conveys that the body is required. Overall it is concise with no significant filler.

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 mutation tool with no annotations and no output schema, the description is incomplete. It fails to explain return values, error conditions, or how the upsert behaves when multiple items match the same unique property. The schema covers inputs well, but the description alone is insufficient for agents to use the tool confidently.

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% and the only parameter 'inputs' is fully described in the schema. The description adds no new parameter semantics beyond telling the user to 'Check the inputSchema for required body structure,' which is redundant given the schema is already available.

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 operation: 'Create or update a batch of line items by unique property values.' This specifies the verb (create/update), the resource (line items), and the distinguishing mechanism (unique property values), which differentiates it from sibling batch-create and batch-update tools.

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 on when to use this tool versus alternatives like batch-create or batch-update. The only instruction is that a body parameter is required and to check the input schema, which does not help the agent choose between the many sibling tools.

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