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

Adds substantial behavior beyond the annotations: the return is masked, the full text is never exposed to agents, and set is strictly limited to free-text plus region. What it doesn't state outright is that `set` replaces any existing default — though destructiveHint=true in annotations signals this, the description could confirm it explicitly.

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?

Front-loaded with the core read/set split and bulleted so the masking rule and the set-field constraint are easy to scan. Slightly redundant with the schema on character limits (≤200/≤40 appear in both places).

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 supplies the read payload shape ({ has_default, address_region, masked_summary }) and explains the handler-side resolution path, which is exactly the missing piece. Nothing an agent needs in order to call this correctly is absent.

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 the baseline is 3, but the description genuinely adds meaning: only two fields are valid on `set`, no structured recipient/line1/city/phone fields exist, and the agent must concatenate the address itself. That is real guidance the schema alone does not convey.

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 verb pair and resource ("Read (masked) or set your default shipping address") and situates it in the wider flow (feeds webaz_search's unshippable filter, webaz_demand's default region, webaz_place_order resolution). It never contrasts itself with the sibling webaz_address, which is the one ambiguity an agent might have.

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 concrete when-to-use guidance: read when you only need masked data, omit shipping_address in webaz_place_order to use the stored default, and handle full-text management in the PWA profile instead of this tool. No explicit 'do not use this when…' relative to webaz_address.

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