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

With no annotations provided, the description carries the behavioral transparency burden. It discloses that titles are discarded and that the count is of current stories, implying a read-only live fetch. It does not mention error behavior, network dependency, or how the nine optional schema parameters are treated, leaving some behavior opaque.

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?

Two short sentences with no filler. The primary action is front-loaded, and 'Titles discarded' is a useful, non-obvious clarification stated in a single phrase.

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 zero-required-parameter counting tool, the core return behavior is stated. However, given nine optional parameters and no output schema, an agent cannot tell whether the tool accepts a feed or URL to count a different source or whether all parameters are ignored. This is the main completeness gap.

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%, so the baseline is 3; the schema already documents each parameter. The description adds no mapping between the tool and the nine optional parameters, so an agent cannot tell from the description which, if any, parameter should actually be supplied for hn-front-count.

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 operation ('Count') and a specific resource ('current Hacker News front-page stories'), and 'Titles discarded' clarifies that the result is a count rather than article content. It is distinguishable from sibling tools like web-fetch or wiki-title-ok, though it does not explicitly contrast itself with them.

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 intended use is implied: call this when the goal is to know how many stories are currently on the HN front page. However, there is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives, and no indication whether a feed URL or other parameter should be supplied.

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