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 real context beyond them: results are ordered newest first and each carries a date, summary and page link, plus the AND semantics of the word filter. It omits any note on what happens when no matches exist or on result truncation beyond the limit parameter.

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, front-loaded with what the tool returns before the narrowing options, with no filler. The parenthetical list of content types is slightly clunky but earns its place by defining the news domain.

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?

With no output schema and no required parameters, the description fully compensates by naming the returned fields, their order, and the three filtering dimensions. An agent has everything needed to invoke it correctly without opening 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?

Schema description coverage is 100%, with the site enum values and limit bounds fully documented in the schema, so the baseline of 3 applies. The description only restates the filter axes in prose ('words in the headline or summary', 'by topic') without adding format hints, multi-topic behavior, or matching rules beyond the schema's own wording.

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 (search/published stories) and resource set (Stories Lounge Frog, Cruises Frog, Points Frog) with the content domain spelled out via examples (lounge openings, program changes, cruise news, points and miles news). An agent can tell this returns published news items rather than entities. It does not, however, differentiate itself from the sibling list_news or list_cruise_news, so it falls short of a 5.

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 final sentence implies usage by listing the narrowing axes (site, headline/summary words, topic), which tells an agent how to scope a search. There is no explicit when-to-use vs list_news/search_app_content guidance and no statement of when this tool is the wrong choice, so guidance remains implied rather than stated.

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