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

Goes far beyond the annotations (which only cover read-only/idempotent safety): it discloses the return shape, the exact distinct status values, that the list is historical rather than a single current state, that order is not chronology, that an empty list proves nothing, what event types are omitted, that no timestamps/links are returned, and that request failures error rather than return empty. It also adds a rate-limit guideline (>=3s spacing, no concurrent polling).

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?

Purpose, then constraints, then return semantics are front-loaded and mostly information-dense. It is long for a one-parameter read tool and closes with somewhat generic boilerplate ('Use only the declared fields. Ask for missing facts instead of inventing values'), which costs a point.

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?

Even though an output schema exists (so return values need not be explained), the description still supplies the interpretive context an agent needs: what each status value means, how to read an empty result, and what is omitted. Nothing needed to call or interpret this tool is missing.

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% and there is a single required parameter, so the schema already carries the semantics. The description reinforces the documentId semantics (use the actual UUID, not fileId/trackingId/operationId, no placeholders) but adds little beyond what the schema field description already states, so the baseline of 3 is appropriate.

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 document status events') and explicitly bounds scope by naming what it does not do (upload, prepare, send, sign, poll continuously). This cleanly separates it from the three state-changing siblings without requiring the agent to open any 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?

Gives clear when-to-use context ('after preparation/sending, especially pending or UNKNOWN_OUTCOME') and when-not guidance (not continuous polling, a status check does not authorize retrying a state-changing tool). It does not name the sibling tools as explicit alternatives, leaving that inference to the agent, which keeps this just short of a 5.

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