Get Headlines

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

The readOnlyHint annotation already communicates the safety profile, and the description's 'Get' verb is consistent with that. The description adds no extra behavioral context such as pagination, result ordering, or handling of empty results, so it does not go beyond the annotations, but it also does not mislead.

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?

The description is a single, front-loaded sentence with no filler. It communicates the core action first and then mentions filtering, making it easy to parse quickly.

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 7 optional parameters, no output schema, and sibling tools like search-news, the description should help the agent choose the right tool and invoke it correctly. It only covers three filters and gives no guidance on the role of max or the AI-based filters, nor does it explain how it differs from search-news. This leaves material gaps for the agent.

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 the baseline applies. The description merely names three of the seven filters (country, category, language) without adding any meaning beyond the schema, and it ignores the AI-related and max parameters. It neither enriches nor contradicts the schema.

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 uses a specific verb and resource ('Get top headlines') and clarifies the main function, distinguishing it from a general search by focusing on headlines. However, it does not explicitly contrast with the sibling tool search-news, and it omits several available filters (max, ai_sentiment, ai_entity_name, ai_entity_type), 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 description gives no explicit guidance on when to use this tool instead of search-news or usage. It only states that filtering is optional, leaving the agent to infer the appropriate context without any comparison to alternatives.

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