post-crm-v3-objects-line_items_line_items

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. It only repeats the mutation implied by the verb 'Create' and the schema-required body, without explaining side effects, authentication needs, rate limits, or return format. The description adds no meaningful behavioral context beyond what the tool name already implies.

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 brief (two sentences), but this is under-specification rather than conciseness. The first sentence 'Create.' is content-free and wastes an opportunity to convey purpose. Only the second sentence provides any value by directing users to the schema.

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?

The tool has nested objects, no output schema, and no annotations, so the description should compensate with richer context. It fails to describe what a line item is, how properties should be structured, whether associations are optional, or what the response will look like. The pointer to the schema is helpful but insufficient for a create operation.

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%, so the baseline is 3. The description adds no parameter-level meaning beyond referring to the input schema. The phrase 'Check the inputSchema for required body structure' is a directive but does not explain properties or associations semantics. It meets the baseline because the schema itself is well-described.

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 states only 'Create.' without specifying the resource or object type. While the tool name includes 'line_items', the description itself fails to mention what is being created, making it indistinguishable from other post-crm-v3-objects-* tools. The verb 'Create' is tautological with the POST method and provides no differentiation.

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?

There is no guidance on when to use this tool versus alternatives like batch-create or search. The note 'REQUIRES body parameter with request data' is about parameter requirements, not usage context. No exclusions or alternative tool references are provided.

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