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

With no annotations, the description must carry the full burden of behavioral disclosure. It only mentions 'Titles discarded,' which hints at output behavior, but it does not disclose whether the tool makes network requests, has side effects, or explain how the nine optional parameters are used. This is a significant gap for a tool with no annotation support.

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 short and front-loaded with the action: 'Count current Hacker News front-page stories. Titles discarded.' It is efficient and avoids verbosity, though it may be under-specified. Still, for the limited content, it is concise.

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 has 9 optional parameters and no output schema. The description does not explain the role of any parameter, the expected output format, or any behavioral details beyond the title-discarding note. For a tool with this many parameters, the description is inadequate for an agent to invoke it correctly.

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?

Schema description coverage is 100%, with each of the 9 parameters explicitly described in the schema (e.g., 'Git ref name; discarded after the shape check'). This meets the baseline of 3. However, the tool description adds no extra meaning about how these parameters relate to counting HN stories, leaving an unexplained disconnect.

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 a specific verb and resource: 'Count current Hacker News front-page stories.' It is unambiguous about the core action. It does not differentiate from siblings, but none of the sibling tools appear related to HN counting, so the clarity is sufficient for a 4.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, and no context about prerequisites or typical use cases. The description is a single sentence that only states the action.

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