hn_show_hn

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

With no annotations, the description fails to disclose any behavioral traits such as ordering, pagination, rate limits, or whether it returns a list or single item. The agent gets no insight beyond the basic purpose.

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?

The description is minimal, but it does front-load the purpose. However, the extreme brevity compromises usefulness, so it scores average for conciseness.

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 tool with one optional parameter, the description should at least clarify the default behavior (e.g., number of posts returned, sorting). Without annotations or output schema, it leaves significant gaps for the agent.

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?

The single optional parameter 'limit' has no schema description (0% coverage) and the description does not explain its meaning or effect. The agent cannot determine what values to use or what the limit controls.

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 it retrieves Show HN posts from Hacker News, using a specific verb and resource. It distinguishes well from sibling tools like hn_top_stories or hn_new_stories, which target different story 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?

No usage guidelines are provided. The description offers no guidance on when to use this tool versus alternatives (e.g., hn_top_stories vs hn_show_hn), leaving the agent to infer context.

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