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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The word 'public' hints that this is a read-only, unauthenticated lookup, but nothing explains outcomes, limits, or error conditions. This is minimal and under-specified.

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 very short and free of filler, which is efficient. However, it is too under-specified to be considered well-structured; it reads as a label rather than a functional description.

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?

With one parameter, no annotations, and no parameter explanation, the description is incomplete for correct invocation. The presence of an output schema reduces the need to describe return values, but the missing q semantics and usage context leave a significant 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 0%, and the description does not explain the lone parameter q. It is not stated whether q is a username, a URL, an ID, or something else. The description adds no meaning to the input schema.

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 identifies the resource (Lobste.rs) and the data returned (public user profile and karma). It lacks an explicit verb like 'get' or 'look up,' but an agent can infer the tool's purpose. It is distinguishable from sibling profile lookups by naming the specific platform.

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 given about when to use this tool or how it compares to siblings. There are no examples, no mention that q is a username, and no exclusions or alternatives. The agent must guess when this tool is appropriate.

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