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

Adds useful behavior beyond the annotations: the count caveat versus the PWA aggregate badge and the explicit exclusion list tell the agent what it will and won't see. However, annotations declare readOnlyHint=false and destructiveHint=true, and the description never discloses that the mark_read option irreversibly clears unread state — the most consequential behavior here goes unmentioned.

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 tight sentences, front-loaded with purpose then scope. There is minor redundancy between 'excludes chat' and 'For order chat use webaz_order_chat', but both clauses carry routing value.

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?

No output schema exists, yet the description covers what is returned (orders/shipping/disputes), what is not, and why counts may differ from the PWA badge. Combined with fully described parameters and annotations, an agent has what it needs to call this correctly.

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%, so all three parameters (unread, api_key, mark_read) are already documented with defaults. The description adds no parameter-level meaning, 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?

States a specific verb and resource ('Read system notifications') and immediately narrows the scope with a parenthetical domain list (orders/shipping/disputes). It also names the sibling it is not (webaz_order_chat), so an agent can distinguish it from the chat-family tools without opening either 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?

Explicitly excludes chat, announcements and feedback, and routes order-chat needs to webaz_order_chat — clear positive and negative conditions. It stops short of saying when this tool is preferable to inspection tools like webaz_buyer_orders or webaz_get_status, which would be needed for a 5.

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