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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and "Rein lesend" merely restates that. The description does add one piece of non-annotation context: the call returns metadata and/or content. It says nothing about behavior when the identifier is unknown, whether content is inlined or by reference, or size/access 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?

Purpose is front-loaded, followed by usage condition and alternatives in two compact sentences. The trailing "| EN: file, image, document, attachment, upload" keyword block is search metadata rather than agent guidance and slightly dilutes the signal, including the somewhat misleading "upload".

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 one-parameter, read-only tool with full annotations and 100% schema coverage, the description covers what it does, when to use it, and which siblings handle the adjacent cases. The residual gap is the ambiguous "Metadaten und/oder Inhalt" return shape, which is not disambiguated anywhere since there is no output schema.

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 the object_id contract (32-hex udid) is already fully documented in the schema; the description only restates it as "Kennung". It adds no format, source, or discovery hint for obtaining the id, so the 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 ("Eine Datei aus der strukturierten Ablage abrufen") plus scope (metadata and/or content), and explicitly names the two sibling tools it is not (upload_file_to_object, onto_scope_structuredimage_categories). The only slight fuzziness is "und/oder Inhalt", which leaves what is actually returned open, but an agent can still tell this apart from the upload and category tools.

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?

"Nutze es, wenn du die Datei ueber ihre Kennung kennst" gives a clear entry condition, and the alternative for the opposite case (upload) is named with its tool name. There is no explicit "do not use for X" beyond that, but the routing between retrieve/upload/categories is unambiguous.

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