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

Annotations already cover read-only, idempotent, non-destructive and open-world, and the description goes further by enumerating the three outcome states (received, not-observed, history-unavailable) and warning that absence is not proof of non-delivery. The prompt-injection guidance is relevant for untrusted room content, though it is stated redundantly rather than adding new behavioral detail.

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 purpose and the receiver-only constraint are front-loaded in the first two sentences, and the return states follow logically. The untrusted-data warning is repeated three times in near-identical wording, which is wasted space in an otherwise tight definition.

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, so the description rightly enumerates the possible return states and their limits, and the nested input's cursor workflow is anchored to participant_preflight. What remains missing is how the match is performed (exactness, casing, ordering of multiple candidates), which matters for interpreting a not-observed result.

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 only 50% (text and session are thinly documented), but the description supplies the key semantic: the cursor is receiver-local and the match is on exact sender plus text. It still does not clarify matching rules such as case sensitivity or partial text, so it only partly compensates for the coverage gap.

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 precise verb and resource ('Verify on the intended RECEIVER whether its retained chat contains the exact sender/text after a receiver-local message cursor') and scopes it explicitly against the sibling send/history tools by insisting the check runs in the receiver's session.

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 an explicit negative rule ('Never use the sender's own session') and a scope caveat ('not a human-read receipt or proof of non-delivery'), with the schema pointing to participant_preflight for the cursor. An agent knows exactly the condition under which this tool is the right call and when its result should not be over-read.

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