news.hn-item

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

No annotations are provided, so the description must fully convey behavioral traits. It only states 'fetch a specific item', omitting details like rate limits, error handling (e.g., ID not found), or response format. This is insufficient for a tool with zero annotation support.

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 a single, front-loaded sentence of 8 words. It is efficient, no wasted words, and earns its place by clearly stating the core function.

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 the simple tool with one parameter and no output schema, the description is somewhat complete but lacks details on what is returned (e.g., full item object) or error behavior. It is minimally sufficient but not comprehensive.

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?

With 0% schema description coverage, the description must add meaning. It explains 'by numeric ID', clarifying that the parameter is an identifier. However, it does not specify any constraints (e.g., positive integer, range) or format, leaving the agent to infer. This provides marginal value beyond the schema type.

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 verb 'Fetch' and the resource 'specific Hacker News item', and the method 'by numeric ID'. It distinguishes from siblings like 'news.hn-top' (top stories) and 'news.search' (general search) by specifying item retrieval by ID.

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 when a specific HN item ID is known. It does not explicitly contrast with siblings or provide exclusions, but the context is clear enough that no alternative tools would be mistaken.

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