Get signature document

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

With no annotations provided, the description carries full behavioral burden. It states it includes signing results, which is useful, but does not disclose whether the operation is read-only, requires specific permissions, or what happens if the document is not found. It fails to mention any side effects or limitations.

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 concise and front-loaded: it states the primary function and a key detail (signing results). No fluff or redundancy.

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?

As a simple get-by-id tool with one parameter required allem in schema, the description is minimally sufficient to understand the basic operation Dove. However, given no output schema and no annotations, adding context about response format or errors would improve completeness.

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 0%, so the description must explain the parameter. It does not elaborate on the documentId format (e.g., is it a UUID?) or any constraints. The name implies the documentId identifies the signature document, but that is minimal.

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 it retrieves a single e-signature document with its signing results, using a specific verb 'Get' and resource 'e-signature document'. It distinguishes from siblings like gambot_list_signatures (list all) and gambot_get_signature_link (get link), though it doesn't explicitly name them.

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 implies it is used for retrieving a specific signature document by ID, given the required documentId parameter. However, it does not explicitly state when to use this over siblings like gambot_list_signatures or gambot_get_signature_link, nor provide any alternative context.

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