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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by disclosing that results aggregate data from both visitor reports and the endpoint itself, which is useful behavioral context. No contradiction with annotations.

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, tightly packed sentence that front-loads the core function and the time window before adding data-provenance detail. No wasted words, and the key information appears first.

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, read-only aggregation tool, the description is nearly complete: it states the resource, time scope, and output contents. It does not describe the exact return format, but no output schema exists and the data nature (flights, airlines, counts) is adequately conveyed.

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 has zero parameters, so the baseline is 4. The description goes further by explaining what the returned data contains (flights, airlines, total report counts) and its time scope, adding semantic meaning to the tool's output even though there is no input schema to enrich.

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 clearly states a specific verb-resource pair: it reports the most-reported flights and airlines of today and the last 7 days, including total counts. This distinguishes it sharply from siblings meld_herrie (submitting a noise report) and wat_vliegt_over (live aircraft info).

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?

The description explains where the report data comes from (schipholherrie.nl visitors and this endpoint), giving useful context about data provenance. However, it does not explicitly say when to prefer this tool over its siblings or state any exclusions, though the distinct purpose makes the choice fairly obvious.

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