news_topics

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

Discloses ordering by proprietary algorithm and hourly updates. With no annotations, this provides some behavioral context but no mention of read-only nature or side effects.

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?

Three sentences, all valuable. First states purpose, second gives analogy, third explains update frequency. No fluff.

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 no parameters and no output schema, the description fully explains what it returns, ordering, and update cadence. Complete.

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?

No parameters, so description adds no param info. Baseline score of 4 as per guidelines, and description adds context about algorithm and update frequency.

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?

Clearly states it gets trending topic clusters and stories, ordered by a proprietary algorithm. Mentions analogy to /topics view, distinguishing it from siblings like news_latest or 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?

Implies usage for trending topics via analogy to /topics view, but no explicit when-to-use or when-not-to-use versus siblings like news_latest or search.

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