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

Annotations already declare the write/idempotent/non-destructive profile, so the bar is lower. The description earns credit by disclosing a cross-system side effect ('Libertas honors it across its follow-up systems') that annotations do not convey. It omits auth requirements, but nothing contradicts 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?

Two sentences, front-loaded with the action and its trigger before the identifier guidance. The opening enumeration of channels is slightly wordy given the schema already carries the channel enum, but no sentence is wasted.

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 an output schema present, return values need not be described. Purpose, trigger, cross-system effect, and parameter selection are all covered; only edge behavior (e.g. what happens with no identifier at all) is unstated, which is a minor gap.

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 coverage is 100%, so baseline is 3, and the description goes beyond it by explaining the selection logic with zero required parameters: use quote_id when available, otherwise email and/or phone. That disambiguation is not stated in the schema.

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 specific action (records an opt-out) with a specific scope (phone call, text, email, or all), and the resource is unmistakeable. No sibling tool in the list overlaps with opt-out recording, so the agent can select it without ambiguity.

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?

Gives a strong when-to-use trigger: 'Appropriate whenever the customer asks, in any wording, to stop hearing from Libertas.' It does not name an alternative tool or an exclusion case, but no listed sibling performs this action, so routing risk is low.

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