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

No annotations are provided, so the description carries the burden. It discloses the 25-document limit, the included fields (status, signed-PDF URLs), and the authentication requirement (API key). It implicitly signals a read-only operation via 'List' and does not describe destructive side effects, which is appropriate for this simple tool.

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 two sentences, front-loaded with the core action and scope, and every word adds value. 'Requires a SignSimple API key' is a necessary operational note with no fluff.

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?

Given the tool's simplicity (0 params, no output schema, no annotations), the description is complete. It specifies the count (25), the source (connected SignSimple account), the data returned (status, signed-PDF URLs), and the prerequisite (API key). No significant gaps remain.

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?

The tool has zero parameters, so the description need not explain parameter details. The schema coverage is 100% (vacuously), and the description adds context about the default return set (25 most recent), which is valuable beyond the empty schema.

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 clearly states the verb 'List' and the resource 'documents' with specific scope: the 25 most recent sent from the connected SignSimple account, including status and signed-PDF URLs. This distinguishes it from siblings like list_templates (templates) and get_document_status (single document status).

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?

The description provides clear context for when to use the tool: to list recent documents. However, it does not explicitly mention alternatives or when not to use it (e.g., for single-document status, use get_document_status). This is a minor gap, hence 4 rather than 5.

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