rte_headlines

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

No annotations are provided, so the description carries the full burden. It does add useful behavioral context by saying the headlines are 'fresh' and come from a 'public' section, implying current data and no authentication requirement. However, it does not disclose output shape, number of results, pagination, or failure behavior, leaving partial transparency.

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 short and front-loaded: the first sentence states the core action, and the second adds useful scope. There is some redundancy in repeating 'RTÉ News section' and 'headlines,' but no wasted sentences or irrelevant detail.

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?

This is a simple tool with one required enum parameter and no output schema, so a short description is partially acceptable. Still, since no annotations or output schema exist, the description could usefully state what a returned headline contains or how results are presented. It is minimally viable but leaves clear gaps.

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%: the only parameter is fully defined by its enum and the description 'RTÉ News section slug.' The tool description adds the constraint that exactly one public section is used, but adds no deeper semantic or formatting information beyond the schema. Baseline 3 applies.

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 clearly states a verb and resource: getting RTÉ News section headlines, with the added scope of 'one public RTÉ News section.' It is easy to tell this is a headline-fetching tool, though it does not explicitly differentiate itself from sibling tools like rte_sections, rte_article, or rte_news.

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 guidance about when to use this tool instead of related siblings such as rte_news, rte_sections, or rte_article. There are no named alternatives, exclusions, or conditions. Usage is only weakly implied by the phrase 'section headlines.'

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