hn_top_stories

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

No annotations provided, so description must fully explain behavior. Only says 'Get the top stories,' omitting details like response format, pagination, rate limits, or whether it returns story IDs or full items.

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?

Description is a single short sentence, which is concise, but it lacks structure and fails to convey necessary information beyond the tool's basic function.

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 annotations, no output schema, and one undocumented parameter, the description is severely incomplete. An agent cannot effectively determine how to use this tool or interpret its results.

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?

Schema describes one optional 'limit' parameter with type number but no description. The tool description doesn't mention the parameter or its purpose, leaving the agent to guess what 'limit' controls (e.g., number of stories).

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 clearly states it retrieves top stories from Hacker News, but doesn't distinguish from sibling tools like hn_best_stories, hn_new_stories, etc., which have similar purposes.

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 on when to use this tool instead of alternatives like hn_best_stories or hn_new_stories. No prerequisites or exclusions mentioned.

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