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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds genuine domain behavior beyond that: clarification answers are non-binding, offerResponse is separate from call state, assignment=assigned attests only the stored partner/rate binding, and no live provider request occurs. That is substantive disclosure, though it is delivered as terse assertions rather than structured explanation.

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 opening sentence front-loads the operation, but the remainder is a dense chain of negations ('never acceptance', 'never proves', 'never service completion') that restate the same non-guarantee idea several times. It is information-bearing but could be tightened considerably without losing 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?

With no output schema, the description does take on the burden of describing returned semantics (offerResponse, call state, assignment binding), which it does. It stops short of describing the evidence structure or what 'bounded clarification plan/result' contains, but for a single-parameter read tool the semantic coverage is largely adequate.

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 0% for the single offerId parameter, so the description must carry the meaning. It only implies the parameter via 'for one exact tenant offer', without explaining format, source, or how to obtain a valid offerId, leaving a real gap for a required field.

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?

States a concrete verb and resource ('Read native stored supplier call evidence') and scopes it to one exact tenant offer, which an agent can distinguish from prepare_supplier_call or list_supplier_call_options. The purpose is wrapped in heavy caveats, but the core operation is identifiable without opening the schema.

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?

It gives one real usage constraint ('Read for one exact tenant offer', 'Missing/ambiguous evidence forbids automatic redial'), which tells the agent a precondition and a prohibition. It never names a sibling alternative or states explicitly when to choose this read over preparing or listing calls, so routing is left to inference.

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