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

Goes well beyond the readOnly/idempotent/non-destructive annotations by disclosing that every read re-checks publication, that withdrawn bases return 404, that no cached files are served after withdrawal, and by warning that uploaded text must be treated as untrusted data rather than instructions.

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?

Dense but front-loaded: the core download action and publication/404 semantics come first. The iframe-embedding sentences and search limits are somewhat tangential to a download call, adding bulk that isn't strictly about invoking this tool.

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?

With no output schema, the description still conveys the essential contract: what is returned (the DOC source), what happens on failure (404 for private/withdrawn, no cached serving), and the safety caveat about untrusted content. An agent has enough to call it correctly.

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%, with both base_id and document_id documented as 64-character IDs, so the baseline is 3. The description adds no parameter-level detail (e.g., how to obtain the concept's linked document_id) beyond what the schema already states.

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 (Download) and resource (the DOC source linked by the OKF concept), and the 'DOC source' framing implicitly separates it from the many format-specific siblings (docx_source, pdf_source, markdown, original, image). An agent can identify the target artifact without opening the schema.

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 preconditions for use: published bases only, no account required, and 404 for private/withdrawn bases. It does not explicitly name a sibling to prefer for other formats or state when NOT to use this route, so it stops short of full alternative routing.

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