upload_pdf

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

With no annotations, the description carries full burden. It indicates the uploaded PDF will be referenced by other operations, implying persistence and return of an identifier. However, it omits details on side effects, permissions, error handling, and exact return value, so it is only moderately transparent.

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 two concise sentences with no filler. It front-loads the main action and immediately provides essential usage guidance.

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?

The description covers the primary purpose and parameter choice, but lacks details on return value, error conditions, and behavior of optional parameters. Without an output schema, the agent would benefit from knowing what is returned (e.g., document ID).

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 100%, baseline 3. Description adds the critical semantic constraint that filePath and url are mutually exclusive, which is not in the schema. It does not explain metadata or preSignedUrlExpiresIn, but the main constraint adds value beyond the schema.

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 the verb 'Upload' and resource 'PDF' to PDFGate, and the purpose of making it referenceable by other operations. This effectively distinguishes it from sibling tools like generate_pdf or get_document.

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 explicitly states that either 'filePath' or 'url' must be provided, giving clear usage guidance. However, it does not explicitly mention when to use this tool versus alternatives like generate_pdf, leaving some inference to the agent.

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