Request a document upload link

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

Annotations indicate readOnlyHint=false (mutation) and openWorldHint=true. The description adds context that the process involves a one-time upload page, file bytes never pass through the chat, and the upload token is used subsequently, which enriches the behavioral understanding beyond annotations.

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, consisting of two clear sentences with no extraneous information. It is front-loaded with the core purpose and immediately conveys the usage pattern.

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 tool with one parameter, no output schema, and low complexity, the description fully covers purpose, usage scenario, behavioral expectations, and follow-up steps. It is complete given the context.

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 single parameter 'filename' is fully covered by the schema description (100% coverage). The tool description does not add additional semantic detail about the parameter, so baseline score of 3 is appropriate.

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 explicitly states 'Get a one-time drag-and-drop upload page URL', clearly identifying the tool's verb (get) and resource (upload page URL). It also distinguishes from siblings by detailing the follow-up steps using the upload token.

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 explicit guidance on when to use this tool ('when the document is a local file or a private Google Drive file') and what to do after ('pass the returned uploadToken to create_signing_session, create_envelope, or upload_document'). It could be improved by explicitly mentioning when not to use it (e.g., for direct file upload via chat).

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