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

With no annotations provided, the description carries the burden of disclosing side effects; it only says 'Count' and 'Titles discarded,' but does not state whether the tool is read-only, whether it makes a network request, or what the output format is.

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 short and front-loaded, but the phrase 'Titles discarded' is cryptic and adds ambiguity without contributing useful information.

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 no output schema and 9 optional parameters, the description is incomplete: it does not explain what the tool returns, how the parameters affect the count, or whether they are ignored entirely.

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?

Although all 9 parameters have schema descriptions, many are clearly unrelated to counting HN stories (e.g., 'Git ref name', 'IANA timezone name', 'Search text'), and the tool description does not clarify which parameters are actually meaningful or ignored.

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 names a specific action ('Count') and resource ('current Hacker News front-page stories'), making the tool's purpose immediately clear and distinguishing it from sibling tools like web-fetch or fetch-status.

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 given about when to choose this tool over alternatives; it does not mention relationship to web-fetch, normalize-url, or other siblings, nor any conditions under which it should or should not be used.

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