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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuine behavioral detail beyond that: results are ordered 'featured first' and each item carries page links and ids for follow-up. It stops short of stating default page size or whether all matches are returned, though the schema's limit param covers count.

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 sentence that front-loads the resource and packs the content taxonomy and follow-up pointer without filler. Nothing in it is redundant with the title or restates the 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?

Six optional parameters with no output schema, so the description needs to convey roughly what comes back — it does via 'featured first, with page links and ids'. Annotations cover the safety profile. The remaining gap is per-kind parameter coupling, which neither description nor schema makes explicit.

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 100%, including a verbose enum for kind and a default for limit, so the schema already does the parameter work. The description's parenthetical largely restates the kind enum values rather than adding filtering semantics (e.g. which params are required per kind, or whether metric only applies to top_list). Baseline 3 is appropriate.

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) and resource (Lounge Frog's guides) and enumerates the guide shapes (card-at-airport, program-at-airport, two-card compare, best-on-a-metric, editorial lists), so an agent can tell what content comes back. It also names get_article as the downstream consumer, which separates it from retrieval siblings. It does not, however, distinguish itself from list_news or search_news, which likely surface overlapping editorial 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?

The phrase 'with page links and ids for get_article' gives a clear two-step workflow: enumerate here, then fetch details there. The parenthetical content types also signal when this tool fits a browsing-style query. There are no explicit exclusions telling the agent when to prefer search_news or list_news instead.

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