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

No annotations are provided, and the description does not disclose whether the tool is read-only, makes network calls, has rate limits, or returns partial data. The phrase 'Titles discarded' hints at output filtering but is vague.

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 very concise and front-loaded with the main purpose. However, 'Titles discarded' is ambiguous and the description omits crucial parameter guidance, so conciseness comes at the expense of clarity.

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 a schema full of unrelated optional parameters, the description is not complete enough for an agent to invoke the tool confidently. It does not explain return format, errors, or how parameters relate to the tool's purpose.

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 exposes nine optional parameters (ref, url, city, feed, host, json, path, zone, query) with descriptions that have no connection to counting HN stories. The description adds no clarification about how, if at all, these parameters should be used.

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 states a clear action and target: count current Hacker News front-page stories. However, the input schema is entirely unrelated—no parameter refers to Hacker News—so the clarity is undermined by the mismatch.

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?

The description gives no guidance on when to prefer this tool over the many siblings such as fetch-status, web-fetch, or normalize-url. It does not explain what makes hn-front-count the right choice for a given task.

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