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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is well covered. The description adds meaningful behavioral context: the data source is the public catalogue, ordering is newest change first, and both added and updated items are included. It does not describe pagination or time-window semantics, but the output schema covers the return shape.

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 concise sentences with zero filler. The first sentence defines scope and ordering, and the second gives usage guidance with an alternative. Every phrase earns its place, and no information is repeated from the schema or annotations.

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 single-parameter list tool with an output schema and strong safety annotations, the description covers purpose, data scope, ordering, and sibling differentiation. Nothing essential is missing for correct invocation, and the `limit` parameter is fully constrained by the 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?

The sole parameter `limit` has 0% schema description coverage, and the tool description never mentions it. While the parameter name and schema constraints (default 10, min 1, max 50) make its purpose reasonably inferable, the description fails to add any semantic value or compensate for the absent schema descriptions, which is required for low coverage.

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 ('List'), a well-defined resource ('German flea markets in the public my-flohmarkt.de catalogue'), and a clear ordering ('newest change first'). It also differentiates itself from the sibling search_events by noting that search_events is for city, PLZ, date range, or area queries, leaving no ambiguity about this tool's purpose.

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?

Explicitly tells the agent when to use this tool ('to see what is new without a search query') and when to use the alternative ('use search_events when you know the city, PLZ, date range or area'). This provides direct decision guidance between siblings, though get_event is not mentioned—an acceptable omission since get_event is for retrieving a single known event.

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