post-crm-v3-objects-quotes-batch-upsert_upsert

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 states the basic create/update action and a requirement for a body parameter, but does not reveal important behaviors like idempotency, partial failure handling, permissions, or return values. For a mutation tool, this is a significant gap.

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 only two sentences and is front-loaded with the core verb. The second sentence about the body parameter is somewhat redundant given the schema's required field, but it is brief and does not waste words.

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?

This is a complex batch upsert tool with a nested array structure and no output schema. The description lacks essential context such as return values, error behavior, how unique property matching works, and whether the operation is atomic. It is under-specified for its complexity.

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 description coverage is 100%, so the schema already explains all parameters including inputs, id, properties, idProperty, and objectWriteTraceId. The description adds no new parameter-level semantics, merely directing the user to 'Check the inputSchema.' This meets the baseline but does not exceed it.

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 specific action: 'Create or update a batch of quotes by unique property values.' This distinguishes it from batch-create or batch-update tools for quotes, as upsert behavior is explicitly stated. The verb+resource+mechanism makes the purpose unambiguous.

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 description implies the intended use case (upserting quotes based on unique property values) but does not explicitly mention when not to use it or suggest alternative tools. It provides enough context to infer usage, but lacks explicit exclusionary guidance.

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