list_stories

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

The description discloses return content (titles, URLs, scores, metadata) and pagination, but lacks details on authentication, rate limits, or output structure. Since no annotations are present, it carries the full burden but does not go beyond basic transparency.

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?

One compact sentence, front-loaded with the primary action and resource, and includes necessary details without superfluous content.

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?

Given no output schema, the description adequately specifies the return content and feed types. It is sufficient for a straightforward listing tool, though more detail on the return structure could make it more 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?

Schema coverage is 100%, so the baseline of 3 applies. The description adds the concept of pagination, but the schema already describes each parameter (feed, limit, offset) comprehensively, so no significant additional meaning 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?

The description clearly states the tool's function: browsing Hacker News feeds with specific feed types and pagination. It distinguishes itself from sibling tools like get_item or search by focusing on feed-based listing.

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?

The description implies usage for feed browsing but does not explicitly mention alternatives or exclusions. The context is clear, and the feed types are enumerated, providing adequate guidance without stating when not to use it.

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