aggregate_news

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

Without annotations, the description discloses key behaviors: merging similar events, returning dedup statistics and coverage info. It does not mention side effects or auth needs, but as a read-only aggregation tool, this is acceptable.

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 concise: a one-line summary, a brief explanation, bullet-pointed args with clear explanations, return format, and examples. No superfluous information.

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 complexity (5 params, output schema present), the description covers all aspects: purpose, parameters, return structure, and usage examples. It is self-contained and sufficient for an AI 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?

All five parameters are explained with defaults, ranges, and examples. The description adds meaning beyond the schema (e.g., 'similarity_threshold: 0.3-1.0, default 0.7'), compensating for the 0% schema description coverage.

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 that the tool aggregates news across platforms, deduplicates similar stories, and provides cross-platform coverage and popularity. This distinguishes it from siblings like 'get_latest_news' (simple retrieval) and 'search_news' (query-based search).

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 specifies default behaviors (e.g., 'today' for date_range, all platforms) and provides examples. However, it does not explicitly state when to use this tool versus alternatives, though the context makes it clear (use for cross-platform aggregation).

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