findAskHN

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

With no annotations, the description bears full weight. It only states 'search' but does not disclose behavioral traits such as being read-only, auth requirements, rate limits, pagination limits, or what happens to results. The parameter descriptions partially help but overall transparency is low.

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. It is concise without extraneous words. However, it could be slightly more structured (e.g., first sentence for purpose, second for usage).

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?

The tool has 7 parameters, no output schema, and no annotations. The description fails to explain what the search results contain (e.g., titles, URLs, scores) or how pagination works. This is incomplete for a complex search tool.

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%, so baseline is 3. The description adds some context ('problem discovery and demand signals') but does not elaborate on parameter behavior beyond what the schema provides. Value is marginal over 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?

The description clearly identifies the tool as searching Ask HN posts, with a specific purpose of problem discovery and demand signals. This distinguishes it from sibling tools like findShowHN (which searches Show HN posts) and general search.

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 guidance is provided on when to use this tool versus alternatives like search or findShowHN. The description implies use for problem discovery but does not contrast with other tools or state when not to use it.

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