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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Titles discarded' and 'Count current' implying a network fetch, but does not explain side effects, authorization requirements, rate limits, or how the 9 parameters are processed or discarded. The behavior remains opaque, especially given the mismatch between the description and the schema.

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 only two sentences and front-loads the main action, which is concise in form. However, it is under-specified to the point of being unhelpful; conciseness should not sacrifice essential information. The description is too sparse to guide correct usage.

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 tool with 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool returns (a count? a boolean?), how it interacts with Hacker News, why the parameters exist, or what 'Titles discarded' means in practice. An agent cannot reliably call this tool without extensive external knowledge.

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 coverage is 100%, so each parameter has its own description, but the tool description adds nothing about how these parameters relate to the stated purpose. The parameters seem to be shape-check inputs (e.g., 'Git ref name; discarded after the shape check') that have no apparent connection to counting HN stories. The description fails to bridge this semantic gap, making the parameter usage confusing.

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 verb and resource: 'Count current Hacker News front-page stories.' However, the input schema presents 9 unrelated optional parameters (ref, url, city, feed, etc.) that have nothing to do with counting HN stories, creating a contradiction between the stated purpose and the actual tool behavior. The purpose is clear in wording but misleading in practice.

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?

No guidance is provided about when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or related tools. There is no context for when an agent should select this over the many sibling shape-checking tools, leaving the selection entirely to chance.

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