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

With annotations already declaring readOnly/idempotent/non-destructive, the description adds real beyond-schema context: live publication check on every read, 404 for withdrawn/private, no cached files after withdrawal, iframe embed routes with limits (3–160 chars, 20 results/page). Also flags untrusted-content handling, which is important for prompt-injection safety.

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-loads the purpose well, but then pivots into substantial iframe/embed guidance that is more relevant to a different concern than downloading a PDF, making it denser and less focused than needed.

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?

Covers the download semantics, access rules, and failure modes clearly. Without an output schema, it could say more about what is returned (a PDF stream/URL) or size limits, but the essential context for correct invocation is present.

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% and both params (base_id, document_id) are documented as 64-char API-returned IDs. Description adds no extra param semantics beyond what the schema provides, so the baseline 3 applies.

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 specific verb (Download) and resource (PDF source for an OKF concept), scoped as public/published-only. The sibling family distinguishes formats (pdf/docx/markdown/original/source/concept), and this description makes the PDF-format role 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 scopes when this works: published bases only, no account required, private/withdrawn returns 404. Good ambient guidance, but doesn't distinguish when to pick this vs. public_read_base_source / public_read_base_original for format selection.

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