Get Job Stories

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description does not need to restate those. It adds that the tool returns 'IDs' (not full content) and that they are the 'latest' stories, which is useful context. However, no additional behavioral details (e.g., rate limits, ordering, or data freshness) are provided.

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, clear sentence with no filler. It is appropriately front-loaded and efficient. It could be slightly more informative without losing conciseness, but it is not verbose.

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 read-only tool with good annotations and fully described parameters, the description covers the essential purpose and output type. It does not explain return value structure (e.g., format of IDs), but since there is no output schema and the parameter 'response_format' hints at formatting, it is adequate. The minimal length is acceptable given the tool's simplicity.

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?

All three parameters (limit, offset, response_format) are fully described in the input schema (100% coverage). The description adds no additional parameter meaning, so it meets the baseline but does not exceed it.

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 action ('Retrieve IDs') and the specific resource ('latest Job stories'), distinguishing it from sibling tools that retrieve other story types (top, new, best, etc.).

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 explicit guidance on when to use this tool vs alternatives (e.g., hn_get_top_stories). The description implies it is for job stories, but lacks conditions, prerequisites, or when-not-to-use advice. The context of sibling tools provides implicit differentiation, but the description itself does not contribute.

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