Update opportunity

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

The phrase 'Only the fields you pass are changed' is a powerful behavioral disclosure that describes the partial update nature of the function. This is a crucial operational detail that is not covered by the idempotent or destructive hints in the annotations.

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 definition is extremely concise, fitting all vital functional information into a single, dense sentence. There is zero waste of language.

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 description is highly complete from a calling perspective because it defines the update behavior. A deduction is made only because there is no output schema, and the description does not address what the successful return value might look like.

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?

With only 50% schema description coverage, the description compensates well by listing many functional actions (e.g., 'move it to another stage,' 'mark it Won/Lost'). This adds necessary semantic meaning to the parameters beyond what the schema alone provides.

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 uses a specific verb ('Update') and identifies the resource ('deal'). It clearly details the specific actions the tool performs, such as moving stages, marking Won/Lost, or changing owner/value, immediately clarifying its scope relative to sibling tools like create_opportunity.

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 it does not explicitly name alternatives, the critical guideline 'Only the fields you pass are changed' provides essential context on *how* the tool should be used (partial update), which dictates when it is appropriate versus needing a full replacement.

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