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

Beyond the annotations, the description discloses pagination limits, the next_offset continuation mechanism, fallback to notice text, documents_status and message behavior, copy_with_documents cross-portal pointers, source_url context, and OAuth plus trial/paid plan requirements. This is substantial behavioral context for an otherwise safe read-only tool.

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 purpose is front-loaded, but the description is a single very dense sentence with multiple semicolon-separated clauses. It is information-rich rather than wasteful, but the structure makes it harder to scan than a short multi-sentence or bullet-like explanation.

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?

Annotations cover safety and idempotency, and there is no output schema. The description fills that gap by explaining return-relevant behavior: document list, status and message when text is unavailable, notice fallback, source_url, and cross-portal copy pointer. It is complete enough for an agent to call and interpret the result.

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 only 33%, so the description must compensate. It clarifies the relation between tender_id and slug, explains that each call reads 20000 characters, and tells the caller to pass next_offset as offset for continuation, adding meaning beyond the bare schema.

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 states a specific verb and resource: reading text from a tender's documentation, explicitly naming SWZ, OPZ, attachments, and the specification-first behavior. It also clarifies the lookup keys, tender_id or public slug, making it clearly distinguishable from general tender lookup or file-listing siblings.

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 strongly implied by the detailed description, and the no-document fallback behavior is explained. However, it does not explicitly say when to choose this tool over siblings such as get_tender_file or list_tender_files, nor does it state clear exclusions.

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