zdnet_news

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

With no annotations, the description carries the full behavioral disclosure burden. It adds useful context by noting the data is 'fresh' and comes from the 'public news feed', implying no authentication or pagination concerns. However, it does not disclose the return format or whether only a fixed number of stories is returned, leaving some ambiguity.

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 short and front-loaded with the main action in the first sentence. However, the second sentence partially repeats 'ZDNet top stories', which is mildly redundant, though it does add the 'fresh' and 'public news feed' details.

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 simple, zero-parameter tool with no output schema or annotations, the description is nearly adequate. It tells the agent what it will receive (top stories) but omits any details about the shape of those stories (titles, URLs, publication dates). Since there is no output schema to fill this gap, the description should have provided at least a hint about the returned fields.

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?

There are no parameters in the schema, so the baseline is 4. The description correctly communicates that no input is needed to call the tool, and there is no parameter-related information to add.

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 states a specific verb and resource: 'Get ZDNet top stories.' It is clear this fetches the current top stories from ZDNet. It doesn't explicitly differentiate from the sibling zdnet_headlines, but 'top stories' vs 'headlines' provides enough distinction for a simple feed tool.

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 when-to-use guidance or alternatives are mentioned. The description implies 'use this for ZDNet top stories' but does not explain when to prefer zdnet_headlines, zdnet_article, or other ZDNet sibling tools. For a zero-parameter fetch tool, this is a missed opportunity to route the agent correctly.

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