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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, yet the description still adds real behavioral context: access is re-evaluated on every request, revocation also blocks search/originals/Markdown/OKF/ZIP, the initial grant requires the owner's session with origin and CSRF checks, and responses are private/no-store. Those are access and caching traits an agent cannot get from the annotations.

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 first sentence is front-loaded and useful, but it is followed by a dense block of access-control boilerplate covering search, ZIP downloads, publishing, collection sharing, and CSRF that is mostly generic to the product rather than specific to reading one document. Much of it does not earn its place for 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?

For a read-only tool with full annotation coverage and a complete output-less schema, the definition covers the authorization model adequately. It still omits anything about the response shape (Markdown vs metadata payload), pagination, or document-size limits, and the boilerplate dilutes the tool-specific guidance.

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 all three parameters are documented in-schema (base_id, document_id, organization_id with the membership/OKFIndex requirement). The description adds no per-parameter meaning, so this is the baseline 3 for a schema that does the heavy lifting.

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 opening sentence names a specific verb and resource: 'Read the document Markdown and metadata.' That is clear. However, it never distinguishes this team variant from the many near-identical siblings (get_base_document, team_read_base_markdown, team_read_base_source), so an agent cannot tell from the text why it should pick this tool over those.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The text implies a team-scoped read via the access model, but an agent is left to infer whether this is the team-authorized counterpart of get_base_document or something else.

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