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

Goes well past the annotations (which only cover read-only/idempotent/no-open-world safety): it discloses result ordering, data provenance ('site's published dataset, not a live web search'), freshness semantics ('updated_at is the last scan time'), and a caveat about citing publishers and preserving uncertainty. That is exactly the extra context annotations cannot carry.

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?

Dense but front-loaded: purpose first, then filters, provenance, and pagination. Six short sentences each carry information, though the citation/uncertainty sentence is output-policy guidance rather than invocation guidance and could be trimmed.

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 an output schema present, return values need no explanation, and the description still covers ordering, data source, staleness, and pagination. An agent has everything required to call it correctly, aside from the next_offset naming slip.

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 83%, so the schema already documents limit, offset, since, query, and product; the description only adds that the text search spans titles, summaries, and publisher names. It also refers to 'next_offset', a parameter name that does not exist in the schema (the field is 'offset'), which risks an agent passing an invalid argument.

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?

Specific verb + resource ('Search published news coverage') with scope stated up front, including ordering ('newest first'). The clause 'Returns source reports, not verified release facts' implicitly separates it from the release/rumor siblings, so an agent can route without opening schemas.

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?

Gives clear filtering context (brand, tagged product, publication date, text) and explicit continuation guidance ('Use next_offset with the same filters for more results'). It never names get_releases or get_rumors as the alternative, so the when-not-this-tool case is only implied by the 'source reports vs verified release facts' contrast.

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