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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the parenthetical '(Read-only: liest eine einzelne Datei, keine Änderungen.)' largely restates structured data. The one genuinely new behavioral fact is 'falls vorhanden' – the target file may not exist – but the description does not say what is returned in that case (empty result, error, or null).

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?

Two short sentences with the resource and the filename front-loaded. The parenthetical slightly duplicates the readOnlyHint annotation, but it is brief enough that the redundancy costs little.

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 zero-parameter, no-output-schema tool the description covers what the tool reads, but with no output schema it should state the return shape (raw markdown text, parsed content, or nothing when absent). As written, an agent knows what file is targeted but not what a successful or failing call yields.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the schema cannot be a source of ambiguity. Baseline 4 applies; nothing in the description misleads about inputs.

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 names a specific verb and resource: it returns the SEO-/GEO keyword map, and it even identifies the concrete artifact (seo-keyword-map.md). That is far more precise than the sibling names get_content or get_status, though it never explicitly contrasts itself with those siblings, which could also plausibly return file content.

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?

There is no when-to-use or when-not-to-use guidance and no alternative is named. The only hint is the conditional 'falls vorhanden', which tells the agent the file may be absent, but nothing tells it whether get_content is the fallback or when this tool should be preferred over the generic content readers.

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