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

With no annotations, the description carries the full burden of disclosing side effects, permissions, and edge cases. It only mentions 'Titles discarded,' which is ambiguous and does not clarify that all input parameters are ignored or that the tool is read-only.

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 exceptionally brief and front-loaded with the primary action and target. It wastes no words and immediately conveys the core purpose.

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?

For a simple counting tool, the description is mostly sufficient (it implies a numeric output). However, it ignores the glaring mismatch between the tool's purpose and the input schema, leaving the agent confused about parameter relevance and whether certain inputs are intentionally ignored.

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 description does not explain how the nine optional parameters relate to counting Hacker News stories, and the schema descriptions themselves are unhelpfully generic (e.g., 'Git ref name; discarded after the shape check'). Since the tool clearly needs no input to count front-page stories, the description leaves the agent uncertain about whether to pass anything.

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 action (count) and the resource (current Hacker News front-page stories). It does not directly compare to siblings, but no sibling exists for this specific counting task, so the purpose is adequately distinguishable.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any specific use cases, prerequisites, or why one would call this over other tools like fetch-status or web-fetch.

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