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

Annotations already cover readOnly/idempotent/non-destructive. The description adds useful context beyond them: 'Information only — never investment advice' frames the content, source count (up to three) and cursor paging disclose return shape, and the 48-hour purge window is implied. No rate limits or auth notes, but solid added value.

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-loaded with what the tool returns, then behavior, then paging. Every sentence carries distinct information; no padding or repetition of the title.

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?

An output schema exists, so return values need not be explained. Given moderate complexity and full schema coverage, the description supplies everything an agent needs: scope, query behavior, and paging.

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%, so every parameter is already documented, giving a baseline of 3. The description adds query semantics (with/without) and the 48-hour window tied to the hours param, but no syntax beyond what the schema already provides.

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/list) and resource (news stories) with clear scope: last 48 hours, one country, linked to a listed company/commodity/index/rupee. An agent knows exactly what it gets without opening the 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?

Clearly explains the query-on/query-off behavior ('Without a query it returns the most relevant stories; with one, the stories that mention the query's words'), which tells the agent when the query param matters. No siblings exist, so there are no alternatives to route between, but there are no explicit exclusions either.

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