gambot_list_signaturesList e-signature documents newest first to review signature status. Retrieve pending or completed documents for tracking and follow-up.
List e-signature documents (newest first).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. 'List' implies a non-destructive read and 'newest first' discloses ordering, but the description does not mention pagination, response shape, or any side effects/authorization requirements.
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?
One short sentence with the key action and ordering front-loaded; no filler.
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?
For a simple one-parameter list tool, the description is minimally viable: it names the resource and order. It is incomplete because it does not clarify the default/meaning of limit, pagination, or how this relates to the sibling document/signature tools.
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 schema describes only 'limit' with a maximum of 1000 and no textual description, and the tool description does not mention it. The parameter is fairly self-explanatory and constrained, but the description adds no semantic value for it.
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 uses a specific verb ('List') and a specific resource ('e-signature documents'), and adds a sort order ('newest first'), so an agent knows what the tool returns. It does not distinguish itself from the sibling gambot_list_documents, so it misses the top level of differentiation.
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?
There is no statement of when to use this tool versus gambot_list_documents, gambot_get_signature, or gambot_get_signature_link. The ordering hint implies a listing use case, but no explicit when/when-not guidance is present.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.