time_headlines

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'fresh' and 'public RSS', indicating real-time and open access, but does not explicitly state that this is a read-only operation, nor does it mention any limitations (e.g., number of headlines returned, rate limits, or error behavior). The description is too sparse to fully carry the burden of behavioral transparency without annotations.

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?

Two sentences with zero fluff. The purpose is stated first, followed by a clarifying note about the source. Every word earns its place, and the description is appropriately sized for a single-parameter tool.

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 a tool with one parameter, an enum, and no output schema, the description is nearly complete. It tells the agent what it does and the source of data. It lacks details about the response format (expected since no output schema) and does not mention whether the tool returns a limited number of headlines or all available ones, but these are minor given the tool's simplicity.

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 'section' is fully described with an enum and a description ('TIME RSS section slug'). The description adds no additional meaning beyond what the schema already provides — it simply confirms the tool retrieves headlines for a section. Baseline 3 is appropriate since the schema handles parameter documentation.

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 the action ('Get'), the specific resource ('TIME section headlines'), and the source ('one public RSS section'). It unambiguously distinguishes this tool from sibling tools like time_article (for full articles) and time_sections (for listing sections) by focusing on headlines from a section.

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 implies usage: use when you need headlines from a specific TIME section. However, it does not explicitly mention alternatives or exclusions (e.g., 'use time_sections to list available sections' or 'use time_article for full content'). While the name and description make it clear it's for headlines, there is no direct guidance on when not to use it or how it differs from other headline tools.

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