get_trending_news

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, output format, pagination behavior, or rate limits. The agent gains no insight into the tool's side effects or data handling.

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 short sentence, but it is under-specified rather than concise. It lacks necessary details to be useful, making it insufficient for effective agent understanding.

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 no output schema and minimal description, the tool fails to provide a complete picture. The agent lacks understanding of return values, pagination limits, and the meaning of 'trends', making the tool nearly unusable without 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 input schema has 100% description coverage, with basic details like example values and pagination hint. The description does not add extra meaning beyond the schema, but the baseline is 3 due to high coverage. No enhancement is provided.

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?

Description 'Get articles by trends' is vague; 'trends' is undefined and the tool name 'get_trending_news' suggests trending topics, but the description fails to clarify the selection criteria. Sibling tools like 'get_articles_by_date' are more specific, so this tool lacks precise differentiation.

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?

No guidance is provided on when to use this tool versus siblings. It does not explain what constitutes 'trends' or contrast with other filtering tools, leaving the agent without context for appropriate invocation.

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