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

Goes well past the readOnly/idempotent/non-destructive annotations: it discloses that every read re-checks publication, that no cached files are served after withdrawal, that private/withdrawn yields 404, and adds a prompt-injection warning about treating uploaded text as untrusted data. That is rich, decision-relevant behavioral 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-loads the core action well, but then drifts into iframe embedding guidance (embed_url, 3–160 search characters, 20 results per page) that is tangential to invoking this download tool, diluting an otherwise tight description.

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 carries the return-value burden and does so reasonably: it names Markdown output and the 404 failure mode, which is what an agent needs. It does not describe the Markdown payload shape, but for a simple public read that is a minor gap.

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% and both parameters are documented as 64-character IDs in the schema. The prose adds no syntax, format, or constraint detail for base_id/document_id, so it earns only the baseline 3.

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 ("Download document Markdown") and pins the scope to published bases. The format word "Markdown" implicitly separates it from the source/pdf/docx/original/image siblings, though it never names them explicitly.

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 concrete eligibility conditions (published bases only, no account required) and an exclusion (private or withdrawn bases return 404), so the agent knows when this call is valid. It stops short of routing the agent between this and the other public_read_base_* format variants.

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