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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts beyond that: menus are stripped from the payload, and long pages are truncated after max_chars with a stated default of 60000, which tells the agent output may be incomplete.

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?

Three short sentences, front-loaded with the return format before input requirements and the truncation caveat. No filler; the only slight friction is saying 'url or path' while the parameter is named url, which takes a beat to reconcile.

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 two-parameter, no-output-schema tool this is nearly complete: return format, menu stripping, truncation, and both accepted input forms are covered. What remains unstated is error behavior for invalid or off-site URLs and whether the relative path is resolved against kipode.de.

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 0%, so the description must carry the parameters, and it does: it clarifies that the url field also accepts a site-relative path (e.g. "/insolvenzen/") and explains what max_chars controls plus its default. Only the schema's min/max bounds for max_chars are left to the schema itself, which is a minor omission.

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: returns a kipode.de page as clean Markdown, and even enumerates what is kept (text, tables, sources) and stripped (menu). It scopes to kipode.de but never names the siblings (suche, themen, aktuelles) to differentiate itself from them explicitly.

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?

Gives concrete input examples (a full URL and the relative path "/insolvenzen/"), which implies how to call it, but there is no statement of when to prefer this over sibling tools like themen or suche, nor any when-not guidance such as non-kipode.de URLs.

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