HN Pulse

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

Annotations provide only title, so description carries full disclosure burden. It adds valuable semantic context that Show HN contains projects/tools, but omits operational details: no mention of what 'recent' means (time window), rate limits, caching behavior, or pagination. No contradiction with 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?

Single sentence with zero waste. Front-loaded with action ('Fetch recent Show HN posts') followed by clarifying em-dash explaining domain semantics. Every word earns its place.

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?

Appropriate for tool complexity: output schema exists (covering return values), only 1 parameter with 100% schema coverage, and content type is clearly identified. Minor gap: 'HN' abbreviation assumes familiarity with Hacker News; explicit mention of 'Hacker News' would improve completeness for agents without that 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% (count parameter fully documented with range 1-20). Description does not reference the count parameter or add syntax/format examples, so baseline 3 applies per rubric guidelines for high-coverage schemas.

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?

Excellent specificity: uses concrete verb 'Fetch' with resource 'Show HN posts' and distinguishes from siblings (Ask HN, Job Listings, Top Stories) by defining the content type as 'projects and tools shared by the HN community.' The em-dash construction efficiently differentiates this curated category from other HN content types.

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 usage through domain terminology ('Show HN' = projects/tools), helping distinguish from Ask HN (questions) or Job Listings. However, lacks explicit when-to-use guidance or named alternatives (e.g., 'use GetNewStories for chronological content').

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