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

Annotations already declare this as destructive and non-read-only; the description adds useful behavior beyond that: tombstone and audit records remain, recall is limited to the user's own message and a 2-minute window, and conflicts require rereading. The main gap is that 'reread conflicts' is terse and does not fully explain conflict handling.

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 description is very compact and front-loads the core action and constraints, but the fragmentary style and abbreviations like 'chat:recall' reduce readability and structure. It earns most of its space but is too cryptic to score highly.

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?

For a destructive mutation with three required parameters and no output schema, the description covers scope, timing, persistence, exclusions, and the source of IDs/revision. However, it does not sufficiently clarify parameter meanings or exact conflict behavior, so it is only adequate overall.

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%, so the description must carry parameter meaning. It only vaguely points to 'IDs/revision via webaz_order_chat' and does not explain order_id, message_id, or expected_revision individually, leaving key invocation semantics to inference.

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 states a specific verb-resource pair ('recall' a chat message) and scopes it to the user's own message with a 2-minute limit. It also distinguishes the tool from webaz_order_chat by saying IDs/revision come from that sibling, though the telegraphic phrasing makes it less immediately clear.

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 clear prerequisites ('Get IDs/revision via webaz_order_chat'), exclusions ('no recall of formal records, notifications or screenshots'), and a key constraint ('2min'). It does not explicitly compare against webaz_order_chat_edit, so it falls short of fully specifying alternatives.

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