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, or network usage. The only behavioral note is 'Titles discarded,' which is insufficient to understand whether the tool is read-only, makes external requests, or has other implications.

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 brief and to the point, using just two sentences to convey the core action and a behavioral detail. It is easy to parse and does not waste words, though it lacks any structured introduction to parameters or additional context.

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 appears simple, but the description is incomplete because it fails to connect the nine unrelated parameters to the tool's purpose. The expansive and contradictory schema makes the tool's behavior ambiguous, and the absence of an output schema or explanation of parameter usage leaves significant gaps in understanding.

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 lists nine parameters, each with descriptions that are entirely unrelated to the tool's stated purpose (e.g., 'Git ref name', 'HTTPS URL to normalize or cite', 'City name for a public weather hint'). The tool description does not explain how any of these parameters relate to counting Hacker News stories, and the schema descriptions appear to be copy-pasted from other tools, rendering them misleading.

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 specifies the action (count) and the target resource (current Hacker News front-page stories). It also adds a behavioral nuance ('Titles discarded'), which further distinguishes the tool's exact purpose from generic fetching or searching tools.

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 does not provide any guidance on when to use this tool compared to alternatives like web-fetch or fetch-status. It gives no context about the typical use case or limitations that would help an agent decide between tools.

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