HN Pulse

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

With only a title annotation provided, the description carries full behavioral burden. It adds valuable content context ('YC companies and community job posts') indicating data characteristics, but omits operational details like rate limits, caching behavior, or authentication requirements.

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 efficient sentence with no waste. Front-loaded with action verb and clear scope. The parenthetical detail earns its place by clarifying content source without verbosity.

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 a simple read-only tool with one optional parameter and an existing output schema. Description adequately covers intent and data domain without needing to explain return values or complex nested structures.

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% for the single 'count' parameter which is fully documented in the schema. Description provides no additional parameter semantics, warranting the baseline score of 3 for high-coverage scenarios.

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?

Employs specific verb 'Fetch' with clear resource 'job postings' from 'Hacker News'. Parenthetical '(YC companies and community job posts)' clarifies data scope and effectively distinguishes this from story-focused siblings like GetTopStories or GetAskHn.

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 resource type (jobs vs stories/users) provides implied usage context that distinguishes it from siblings, but lacks explicit when-to-use guidance or comparisons to alternatives like SearchStories that might also return job-related content.

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