list_envelope_documents

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

No annotations are present, so the description carries the full burden. 'List' implies a read-only operation, but there is no disclosure about side effects, required permissions, or pagination behavior. The Returns line is too vague to meaningfully enhance transparency.

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 compact and follows a clear Args/Returns structure with no filler. The Returns line may duplicate output schema details, but the overall presentation is efficient and scannable.

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 (one required parameter, read-only listing) and the presence of an output schema, the description provides the core purpose and argument. However, it omits any context on error conditions, authorization, or the structure of returned documents, which could be helpful but may be covered by the output schema.

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 input schema defines only envelope_id as a required string with no description. The description adds 'The envelope ID to query,' which clarifies the parameter's purpose but lacks format examples or guidance on obtaining the ID. This minimally compensates for the low schema coverage.

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 a specific action ('List all documents') on a specific resource ('an envelope'). This distinguishes it from sibling tools like list_envelopes or download_envelope_document. The verb and resource are unambiguous.

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 implicitly indicates this tool is for retrieving documents from a specific envelope, but it does not explicitly compare to alternatives such as list_envelopes or provide exclusions. The intended use case is understandable from context, though not formally guided.

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