post-crm-v3-objects-quotes-batch-create_create

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

With no annotations, the description must disclose behavior but only says 'Create' and mentions a 'body parameter' that conflicts with the schema (which expects 'inputs' directly). The example uses a 'body' wrapper, creating confusion. No side effects, permissions, or return details are disclosed.

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 action. The example is somewhat verbose but necessary to illustrate structure. The 'REQUIRES body parameter' phrasing is awkward but not overly wordy.

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 tool supporting properties and associations, the description omits guidance on associations, required fields, response format, or error handling. With no output schema or annotations, this is insufficient for reliable invocation.

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?

While schema coverage is 100%, the descriptions are generic. The example adds property names but wraps them in a 'body' object not present in the schema, misleading agents about the expected input structure. This negative addition outweighs the baseline of 3.

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 'Create a batch of quotes,' clearly specifying the verb, resource, and batch scope. This distinguishes it from siblings like batch-read, batch-archive, and single-create 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?

The word 'batch' implies us for creating multiple quotes at once, but there is no explicit guidance on when to use this vs alternatives like single create or batch upsert. 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.