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

Beyond the annotations, the description reveals that URLs are short-lived and instructs the agent to share links rather than save files on the MCP host. It does not contradict the annotations, though it omits the CONFIRMATION_REQUIRED/confirm_token flow.

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 four short, purposeful sentences with the main behavior front-loaded. No filler or redundant restatement of the schema.

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?

With no output schema and low parameter schema coverage, the description needs to carry more weight. It does not explain what envelope_id/item_id refer to, how confirm_token should be obtained beyond the schema, or how long the links remain valid.

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 33% and the description does not explain the required envelope_id or item_id parameters. The brief 'one presigned HTTPS link per PDF' hints at item granularity but does not compensate for the missing parameter definitions.

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 opens with a specific action and resource: 'Return short-lived browser download URLs for signed PDFs.' It clearly identifies the tool's output, though it does not explicitly distinguish it from sibling tools like getsign_get_document_url.

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 explicitly states when to invoke: after 'getsign_status action=history reports workflow_completed' or when the user asks to download signed documents. It does not spell out when-not-to-use or name alternative tools, so it stops 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.