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

With no annotations, the description should disclose any side effects or permissions. It does not mention whether the operation is read-only, makes external requests, or has any limitations, which is a significant gap for a network-related tool.

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 extremely concise, consisting of a single clear sentence. It avoids unnecessary detail and is well-structured for quick comprehension.

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 description is incomplete for the tool's complexity. It fails to explain how parameters relate to the task, what inputs are expected, or what output format to anticipate. The mismatch between the description and the parameter list leaves the agent without essential context.

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 parameter list is entirely mismatched with the tool's stated purpose. The descriptions for parameters like 'url', 'city', and 'query' reference unrelated concepts (normalization, weather, length checks), providing no meaningful guidance for counting stories. The schema coverage is 100% but the descriptions are 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 states the action (count) and the target (Hacker News front-page stories). It is specific enough to understand the tool's core function, though it does not explicitly contrast with sibling tools like web-fetch or fetch-status.

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 over alternatives. It only states what it does, leaving the agent to infer appropriate usage contexts.

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