get_news

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses meaningful behavior: only the last ~90 days, newest-first ordering, syndicated duplicates merged, and a strong caveat that these are listings, not verified facts. This materially helps an agent use the results safely.

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?

Every sentence earns its place: definition and output format, use case, time coverage, and trust/citation caveat. It is compact, front-loaded, and free of filler.

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, the description compensates by listing the returned fields, ordering, deduplication, time range, and reliability caveats. The parameter semantics are fully covered by the input schema, so nothing essential is missing for an agent to call this tool correctly.

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 query, days, limit, and language. The description adds no parameter-specific detail beyond what the schema provides, such as language options or limits, so the baseline score of 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?

The description opens with a specific verb and resource: 'List recent news articles about a company or topic,' and immediately lists the output fields, ordering, and deduplication behavior. It clearly distinguishes this tool from asset/search and price tools by focusing on news listings.

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 description gives explicit use cases: explaining what happened around a price move or adding context to a report. It does not mention when not to use it or compare it with sibling tools, so it lacks explicit alternatives-based routing, but the usage context is clear.

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