get_document_pdf

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

With no annotations, the description carries the full burden. It does disclose the return encoding (base64), which is genuinely useful for an agent handling the payload, but it says nothing about session/auth requirements (relevant given the login/session_status/logout siblings) or size/rate limitations.

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?

A single front-loaded sentence with no waste: action, scope, source, and format all in one line. Nothing is redundant or padded.

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 simple 4-identifier read tool with no output schema, the description usefully names both the source of the IDs and the response format. The remaining gap is the unstated authentication/session prerequisite implied by the sibling login tools.

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% — each of the four SAP fields (DOKAR, DOKNR, DOKVR, DOKTL) is documented inline — so the baseline of 3 applies. The description adds no additional meaning about the parameters beyond pointing at their source.

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 (Download), a scoped resource (one document, sourced from list_documents), and the output format (PDF, base64). This cleanly separates it from the list_documents sibling, which only enumerates documents.

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?

"from list_documents" implies the intended workflow — call the list tool first to obtain the identifiers — but there is no explicit when-to-use/when-not statement or mention of alternatives. Usage is implied rather than prescribed.

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