post-crm-v3-objects-line_items-batch-create_create

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only mentions the requirement for a body parameter and provides an example. It does not explain what happens on partial failures, whether the operation is atomic, or what the response contains. This is a significant gap for a batch write operation.

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 three sentences with a practical example, no redundant information, and the purpose is front-loaded.

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, the description omits key contextual information such as response format, error handling, batching limits, and whether partial success is possible. The schema descriptions for nested objects are incomplete (recursion limit reached), so the description should have compensated, but it relies on a minimal example.

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?

The schema covers 100% of parameters, so the baseline is 3. The description adds a concrete example showing the structure of the 'body' and 'inputs' parameters, which is helpful. However, the example uses contact-like properties (firstname, lastname, email) which may not match actual line item property names, and it does not clarify the associations or objectWriteTraceId fields beyond the schema's limited 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 'Create a batch of line items', specifying the verb and resource, and the example further clarifies the expected input format. This distinguishes it from sibling tools like batch-read, batch-update, and single line item create.

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?

While the description confirms this is for batch creation and requires a body parameter, it does not explicitly contrast this with the single-create endpoint or mention when to prefer batch over single operations. There is no guidance on exclusions or limitations.

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