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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the enumerated signer states (waiting, to sign, opened, signed, declined), the condition under which the signed PDF and download link appear, and that the call is free — useful for deciding whether to poll it.

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?

A single tight sentence with the core purpose front-loaded ('Where a signature request stands') followed by the state enumeration and the PDF condition. The trailing 'Free' is a slightly abrupt append but still earns its place as cost information.

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?

There is no output schema, so the description carries the burden of describing the return value — and it does, naming the per-signer statuses and the conditional PDF/link. It falls short only on edge cases (unknown request_id, partial signing) for a single-parameter read tool.

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% and the single request_id parameter is fully documented in the schema, including that esign_send produces it. The description adds no additional parameter detail, 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?

The description states a concrete retrieval purpose — showing where a signature request stands, per-signer status, and the resulting signed PDF — which is more specific than the title alone. It doesn't name or distinguish itself from siblings like esign_list or esign_signing_link, so an agent must infer the boundary itself.

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?

Usage is only implied: read this when you want the status of an existing request or the signed PDF once complete. There is no explicit guidance on when to prefer esign_list (enumerate requests) or esign_signing_link (get a signing URL) instead.

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