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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states the retrieval intent but does not explain effects of max_chars, whether output is truncated, error behavior for unknown document IDs, or any authentication/availability constraints.

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 description is a single, front-loaded sentence with no filler or redundant restatement. Every word contributes to identifying the tool's core action and target resource.

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 and sparse annotations, the description gives a serviceable but incomplete picture. It conveys the main purpose and required input, but leaves max_chars behavior and return format implicit, which an agent may need for fully confident invocation.

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 0%, so the description must compensate. It adds meaning to document_id by calling it a 'known SSearch document ID,' but max_chars is not explained beyond its schema title and default. The description only partially clarifies the parameter semantics.

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 description uses a specific verb ('Retrieve') and a clear resource ('broadered stored text for a known SSearch document ID'). It distinguishes the tool from the sibling search/fetch tools by emphasizing retrieval by an already-known document ID, though it does not explicitly name an alternative.

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?

The phrase 'for a known SSearch document ID' implies the tool should be used when the caller already possesses the document ID, not when looking for documents. However, it does not explicitly say when not to use it or mention alternatives such as search_documents, so the guidance remains mostly implied.

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