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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are 'newest first' and the items are inbound links from third-party publications, which tells the agent what it is actually receiving. It leaves pagination/windowing behavior beyond the limit parameter unstated.

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 sentences, zero filler, with the subject scope and ordering front-loaded ahead of the disambiguation against search_news. Every clause carries information an agent would otherwise have to infer.

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-parameter read-only list tool with no output schema, the description covers provenance, scope and ordering, which is most of what an agent needs. It could still say what an article record contains or how to page past the limit, but nothing essential is missing for a correct call.

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 67% and the description adds no meaning to any parameter — it merely echoes the subject enum values (airport, terminal, lounge, airline) in prose. The ref format nuance ('slug; airports and airlines also take their code') lives only in the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Names the resource precisely (articles from other publications linked from a Lounge Frog page), the four subject types, and the sort order. It also draws an explicit line against the sibling search_news, so an agent can choose between the two without opening either schema.

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 sentence 'search_news has the sites' own stories' gives an explicit alternative and the condition that selects it (external coverage vs. own stories). It stops short of a full when/when-not statement — it never says, for example, that you need an existing subject ref or that list_articles covers non-entity articles.

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