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

With no annotations supplied, the description carries the full burden. It reveals only that titles are discarded and that a count is returned, but it does not disclose whether parameters are ignored, whether network access is used, or what errors or edge cases might occur.

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 with the core action and target. The extra sentence 'Titles discarded' is unnecessary but not verbose enough to significantly hurt the score.

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 description omits important context such as whether the tool relies on live network access, whether the count is approximate or exact, and what output format to expect. The bizarre schema also raises unanswered questions about why unrelated parameters are listed, leaving the tool's actual contract ambiguous.

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 schema includes nine optional parameters, all with descriptions like 'Git ref name; discarded after the shape check' or 'City name for a public weather hint; discarded after the call'. These are semantically unrelated to counting Hacker News front-page stories and actively confuse the tool's purpose. The schema coverage is technically 100%, but the descriptions add misleading rather than helpful meaning.

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 tool counts current Hacker News front-page stories, identifying both the action and the resource. However, the odd phrase 'Titles discarded' adds a minor distraction and doesn't clarify whether the count is of story items or distinct submissions.

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 for when to use this tool over alternatives. With many sibling tools like web-fetch, fetch-status, and search-query-len, the description provides no contextual cues for selecting hn-front-count specifically.

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