browse_latest_news

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

With no annotations provided, the description discloses key behavioral traits: the feed is chronological and newest first, and it is a contextual browse (no search required). It does not mention pagination or authentication, but these are standard for a read-only list tool and output schema exists.

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 two concise sentences, front-loaded with the primary purpose, followed by usage details. Every sentence adds value without redundancy or wordiness.

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?

Given the tool's low complexity, full parameter coverage, and presence of an output schema, the description is complete. It covers the main use case, suggests parameter combinations, and references a sibling tool (list_categories) for further context.

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?

The schema covers all parameters with clear descriptions (e.g., language de/fr/en, limit 1-200, since/until format, category referencing list_categories). The description adds value by emphasizing the chronological nature and the 'no search query' point, and by recommending combination with other parameters.

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 purpose: 'Browse the latest SIP news, newest first (no search query needed).' It specifies the verb (browse), resource (SIP news), and ordering, distinguishing it from sibling tool 'search_news' which requires a query.

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 advises to combine with 'since'/'until' for date ranges and 'category' for filtering, providing clear usage patterns. It also states no search query is needed, but does not explicitly exclude cases where search_news would be more appropriate.

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