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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds non-obvious behavior: 'not metered', 'Opening changes nothing in the books', and that content past the inline threshold comes back behind a fresh download handle rather than truncated. It also hints at an authentication/authorization step tied to the workspace.

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?

Four sentences, front-loaded with purpose, then content variants, then edge behavior (truncation), then safety. Slight verbosity from repeated 'clear canonical' phrasing, but each sentence carries information.

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 an output schema present, the description needn't detail return values, and it still explains the different content shapes and the threshold/download-handle behavior. Only the relationship to sibling tools (verify, export, list_source_documents) is left unstated.

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%, so both parameters (handle, workspace_tag) are already documented in detail. The description only reinforces that the handle names the document and that a new download handle may appear in the result; it adds no format or constraint detail beyond the schema. 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 a specific verb and resource ('Authenticates one Standard Document named by its transfer handle') and enumerates how each document type opens (statement, chart, declaration, books). An agent can distinguish it from verify_standard_document or list_source_documents 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?

Usage is implied (content review via a transfer handle) but there is no explicit when-to-use / when-not-to-use guidance and no named alternative such as verify_standard_document or export_standard_statement. The agent must infer the boundary from the phrase 'for review'.

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