HN Pulse

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

Annotations provide only redundant title with no safety hints, so description carries the burden. It discloses the ranking algorithm (score and recency) but omits read-only safety, rate limits, or cache behavior. 'Fetch' implies a safe read operation, but explicit confirmation would improve this.

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?

Single sentence of 12 words. Every element earns its place: action (Fetch), subject (current top stories), source (Hacker News), and behavior (ranked by score and recency). No redundancy or waste.

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?

Adequate for a simple read operation with one optional parameter and an existing output schema. Captures the essential differentiator (ranking algorithm). Could be enhanced by noting this retrieves front-page/voted content specifically, but covers the necessary context.

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% ('Number of top stories to return (1-30)'), fully documenting the optional count parameter. Description adds no parameter-specific semantics beyond the schema, which is appropriate given the high coverage baseline.

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?

States specific verb (Fetch), resource (stories from Hacker News), and scope (ranked by score and recency). The ranking criteria implicitly distinguish it from siblings like GetNewStories (chronological) and GetAskHn (category-specific), though it doesn't explicitly name alternatives.

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?

Provides implied guidance through the ranking criteria ('score and recency' vs 'new'), but lacks explicit instructions on when to choose this over GetNewStories, GetAskHn, or SearchStories. No prerequisites or error conditions mentioned.

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