Get top stories

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

Since no annotations are provided, the description fully covers behavior: read-only, idempotent, unauthenticated, 60-second in-memory cache, 10 req/s throttling with burst of 20, error handling for upstream failures. No behavioral gaps remain.

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 long but well-organized and front-loaded. Every sentence adds value given the lack of annotations. Minor verbosity but not excessive.

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?

With a simple single integer parameter and an output schema present, the description covers behavior, caching, throttling, error handling, and usage guidance completely for the tool's complexity.

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 only parameter (limit) has 100% schema coverage with default and range, so the description adds little beyond 'returns story summaries' context. Baseline 3 is appropriate.

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?

Clearly states it fetches Hacker News front-page/top stories from the public Firebase API and returns summaries. Explicitly distinguishes from siblings like search_stories and get_item_thread.

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?

Explicitly says use for 'top', 'front page', or currently popular stories, and lists alternatives (get_new_stories, get_best_stories, search_stories, get_item_thread) for other use cases.

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