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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavior beyond the annotations and schema: the exact fields returned per page including both a human URL and a Markdown URL, and a default limit of 30 which appears nowhere in the input schema. It does not state result ordering or whether more than 200 results can be paged.

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 naming the resource and its return fields, followed by a compact 'Optional:' clause covering all three parameters. Dense but waste-free; only the parenthetical German example list is slightly longer than strictly necessary.

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 three-optional-parameter list tool with no output schema, the description covers enough to invoke it and even describes the payload fields. However, it omits the meaning of the enum values and any pagination or result-order information, which are the remaining things an agent would need to use it confidently.

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 0%, so the description must carry the load, and it names all three parameters: query's matching scope (title/description/URL) plus the practical hint that German terms work best with examples, and limit's default of 30. The main gap is that the four 'type' enum values are restated but never explained semantically, so the agent cannot tell what distinguishes 'themenseite' from 'ki-radar' or 'beruf'.

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 ('Lists kipode.de pages') and enumerates the returned fields (title, description, last update, URL, Markdown URL), which is concrete. It does not explicitly differentiate itself from the overlapping siblings 'suche' and 'aktuelles', so the agent must infer that this is the browse/list endpoint rather than the search endpoint.

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 implied: use it to list pages, optionally narrowing with query or type. There is no explicit when-to-use vs when-not guidance and no reference to the sibling search tool ('suche'), even though the 'query' parameter makes the two functionally adjacent. An agent could guess correctly, but the routing decision is left to inference.

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