patch-crm-v3-objects-quotes-var_var

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

With no annotations, the description must disclose behavior, but 'Update' reveals nothing about mutation semantics, partial versus full update, idempotency, permissions, or return values. This is a critical gap for a 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?

While 'Update' is extremely concise, this is under-specification rather than effective brevity. It is shorter than the tool name and provides no structural benefit, forcing the agent to rely entirely on schema and siblings for meaning.

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?

Given the tool has nested objects, no output schema, and no annotations, the description must provide substantial context. A single word 'Update' is completely inadequate for an agent to understand the operation's scope, prerequisites, or return structure.

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%, and each parameter has a description: quoteId is a path parameter, idProperty identifies unique property, and properties are key-value pairs. The description adds no additional parameter detail, but the schema already carries the burden, so the baseline 3 applies.

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 is the single word 'Update,' which is a tautology of the tool's PATCH verb. It does not specify the resource (quotes) or anything about what is updated, making it impossible to distinguish from the many sibling patch tools like patch-crm-v3-objects-invoices-var_var.

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. There is no mention of criteria for using this quotes-specific patch, nor any exclusions or alternative tool references. The description is entirely silent on usage context.

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