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

With no annotations, the description carries the full transparency burden. It does disclose that the tool surfaces profile-oriented information (karma, age, activity), which is useful behavioral context. However, it omits input requirements, possible error cases, and the meaning of 'activity', so it is only minimally transparent.

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 short and free of filler, which is positive. However, the 'Hacker News:' prefix largely repeats the tool name/title, and the fragment-style phrasing lacks a clear verb or sentence structure. It is concise but under-structured.

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?

Although the tool is simple and an output schema exists, the description fails to explain the single input parameter or when to choose this tool over closely related siblings. It also does not clarify what 'age' and 'activity' refer to, leaving an agent without enough context to invoke it reliably.

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 0%, and the lone 'q' parameter is entirely undocumented in the schema. The description vaguely implies a profile query but never states that 'q' should be a Hacker News username or how the parameter is interpreted. This is a weak compensation for the missing schema documentation.

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 identifies the resource as a Hacker News profile and names the specific data points it returns: karma, age, and activity. It is clear enough despite lacking a verb like 'get' or 'fetch'. It does not differentiate from sibling tools such as hnuser or hnsearch, so it does not earn a 5.

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 closely related siblings like hnuser, hnsearch, or hackernews_front. The description does not state any conditions, prerequisites, or exclusions, leaving the agent to guess the intended context.

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