news.hn-top

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

No annotations provided, so description carries full burden. Mentions return fields including dead/deleted flags, but lacks disclosure of rate limits, authentication needs, or read-only nature. Moderate transparency given no annotations.

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?

Two short sentences deliver key information. No fluff. Could be slightly more structured but very concise and front-loaded with purpose.

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 feed tool with 2 params and no output schema, description covers what it returns and the feed types. Lacks pagination or ordering details but adequate for basic usage.

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 coverage 0%. Description mentions 'kind = top | new | ...' but does not map directly to parameter name or explain 'limit' parameter. Enum values are already in schema, so description adds minimal value beyond what schema provides.

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 fetches Hacker News feed and lists the types of feeds (top, new, best, etc.) and what fields are returned. It distinguishes from sibling tools like news.hn-item and news.search by focusing on feed retrieval.

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?

Description implies usage for fetching HN feeds but does not explicitly state when to use this tool versus alternatives like news.hn-item (single item) or news.search (search). No direct exclusions or scenario guidance.

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