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

The description lists the data returned (karma, account age, recent submissions) but does not disclose any behavioral traits such as required authentication, rate limits, or side effects. Since no annotations are provided, the description carries full burden; it is adequate but not detailed.

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 a single, concise sentence that front-loads key information. Every word adds value with no redundancy.

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?

Despite having no output schema, the description sufficiently covers what the tool does and what data it returns for a simple profile lookup. It is mostly complete given the tool's low complexity.

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 input schema has one parameter 'handle' with no description. The description implies that 'handle' is an HN username by stating it returns a user profile, but does not explicitly clarify the parameter's meaning or format. Schema coverage is 0%, so the description partially compensates.

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 indicates the tool retrieves an HN user profile including karma, account age, and recent submissions. It distinguishes from sibling tools (hn_item, hn_search, hn_show_recent, hn_top) which focus on items or search rather than user data.

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 explicit guidance on when to use this tool vs alternatives. The description only states what it does without providing context on appropriate scenarios or exclusions.

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