HN Pulse

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

Annotations provide only title, so description carries full burden. It successfully discloses the external Algolia dependency and scope (stories AND comments), but omits safety profile (read-only vs destructive), rate limits, or pagination behavior details.

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 sentence front-loaded with the action verb. Every word earns its place—'Algolia' signals external service, 'full-text' clarifies search type, and 'stories and comments' defines scope with zero redundancy.

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?

Adequate given the presence of an output schema and complete input schema documentation. However, with minimal annotations (no hints), the description should ideally disclose auth requirements or rate limits for the Algolia integration to be complete.

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 description coverage is 100%, establishing baseline 3. Description adds context that this is 'full-text search' (clarifying query behavior) and mentions 'comments' (relating to tags parameter), but does not elaborate on specific parameter syntax beyond schema.

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?

Description provides specific verb ('Search'), clear resource ('Hacker News stories and comments'), and distinguishes from siblings by specifying 'Algolia full-text search'—indicating this is a query-based tool versus the 'Get' siblings that fetch specific feeds.

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 versus the sibling fetch tools (e.g., GetTopStories, GetNewStories). The 'Search' naming provides implicit contrast to 'Get', but no explicit 'when to use' or 'alternatives' guidance is present.

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