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

With annotations already declaring readOnly/idempotent/non-destructive, the description still adds real behavioral context: free-tier read limits (3 bases, 20 docs, 256 KiB), continued read access after paid capacity expires, private no-store responses, and the warning that uploaded text is untrusted data rather than agent instructions. Some of it (purchase, upload, publish, removal rules) belongs to sibling tools and dilutes this specific tool's profile.

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?

Purpose is front-loaded, but roughly two-thirds of the text concerns billing, publishing, uploading, and removal behavior that this read tool does not perform. Several sentences (purchase/subscription rules, publish_base, upload replacement semantics) do not earn their place in a read-only tool's definition.

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 2-parameter read with no output schema, the description covers limits and security posture but never says what is actually returned (raw bytes, extracted text, a URL/redirect). That leaves a meaningful gap for a tool whose whole job is fetching an original source file.

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% for both base_id and document_id, so the schema fully documents them as 64-character IDs. The description adds nothing about parameter semantics or formats; 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?

The first sentence states a specific verb and resource ('Read the original source linked by the OKF concept'), which distinguishes it from siblings like read_base_concept and read_base_markdown by narrowing to the 'original source' artifact. It does not, however, explicitly name those siblings in the many similarly-named read_base_* 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?

No sentence says when to call this versus the ~15 other read_base_* variants (original, markdown, docx_source, pdf_source, image, index). The bulk of the text is billing and publishing policy, not selection guidance, so the agent must infer usage from the title alone.

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