Search news statements

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description adds real behavioral context beyond that: results are newest-first, pagination works by passing next_cursor back as cursor, and null means no more pages, plus filter semantics for importance_min and source_type.

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?

Front-loads the purpose in sentence one, then uses tight parameter annotations. Every line earns its place, though several lines duplicate schema descriptions rather than adding new information.

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 an 11-parameter, no-output-schema search tool, the description covers ordering, pagination, and the key filters, and annotations cover the safety profile. It is largely complete, though it could say more about what a 'statement' contains and the unused sector/theme_id/topic_id filters.

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 100%, so the schema already documents all 11 parameters. The description largely restates schema text (limit range, ISO-8601 format, comma-separated symbols, source_type effects), adding only the clarification that since/until apply to the article's publication time. 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+resource ('Search extracted news statements') and adds ordering ('newest first'), which distinguishes it from sibling lookups like get_topic or themes. It does not explicitly name an alternative, but the resource is concrete enough for an agent to recognize.

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?

"Use for 'what is the news saying about X'" gives a clear activation context, and the symbol/source_type lines hint at narrowing behavior. There are no explicit exclusions or named alternatives, so it falls short of a 5.

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