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

Adds substantial behavior beyond annotations: the returned link expires after 24 hours, native ReflowPDF files open from their own source immediately, other PDFs are rebuilt by AI, require a free account, consume AI pages, and display cost in the editor. This is exactly the kind of operational context annotations do not provide.

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 key outcome and link validity are front-loaded, and each subsequent sentence contributes necessary operational detail about source PDFs, AI rebuilding, cost, and input options. 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 complex import operation, the description covers the return link, expiry, rebuild behavior, account requirement, cost visibility, and input forms. Since an output schema exists, it need not explain the response object further.

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 description coverage is 100%, so the schema already documents url, name, and pdf_base64 including the 20 MB base64 limit. The description reinforces that the URL must be public https and that base64 is for small files, but adds little beyond what the schema provides.

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 and resource ('import a PDF', returns a link that opens it in the editor's import and rebuilds it as editable) and explains the two rebuilding paths. An agent can understand what this tool does without opening the schema, and it is distinguishable from simpler document-open tools.

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?

Gives clear context for use: a public https URL or base64 bytes for small files, plus the consequence that non-native PDFs need a free account and consume AI pages with cost shown first. It does not explicitly compare against siblings or state exclusions, so it stops short of a 5.

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