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

Goes well beyond the annotations: it explains that the sandbox usually cannot reach Portant, describes the upload card UI behavior in Claude/ChatGPT, gives the exact curl PUT pattern with Content-Type and Authorization header, and specifies PDF-only with a Word-to-PDF conversion note. Annotations only say this is a non-read-only, non-destructive, non-idempotent call; the description supplies the real operational context.

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?

Front-loaded with the core action, then branches into the two invocation paths and the PDF constraint. Dense but nearly every sentence carries actionable detail; the curl example and card explanation are long but earn their place.

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?

Complete for a zero-parameter tool with no output schema: it covers the trigger conditions, both upload mechanisms, the auth header requirement, the returned identifiers, and the follow-up tool. Nothing needed to invoke it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description adds value by naming the artifacts returned (upload_url for PUT, upload_id for the next call), which is useful even though no output schema exists.

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?

States a specific verb+resource ('Get a place to upload a PDF file') and immediately scopes it to PDFs, distinguishing it from text-handling siblings. The downstream link to send_for_signature makes its role in the workflow 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?

Explicitly enumerates when to use it (file rather than text, sandbox-made PDF, user-supplied PDF, anything over 1 MB) and when not to (do not send base64 from the sandbox). It also names the alternative path (shell PUT via curl) and the required next step (pass upload_id to send_for_signature).

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