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

With no annotations, the description carries the full burden, and it does disclose the returned content categories (abstract, decision, revealed reviews). It says nothing about access requirements, whether unrevealed reviews are hidden or omitted, or rate/visibility constraints, so it is only partially transparent for a read 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?

It is a single compact sentence with the resource and lookup keys front-loaded and no filler. The brevity edges into cryptic shorthand ('read endpoint'), but nothing is wasted.

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 five-parameter tool with no annotations, no output schema, and 40% schema coverage, the description leaves the most important things unstated: valid parameter combinations, what 'd' and 'npub' mean, and how this differs from read_paper. It lists returned fields but not enough to call the tool confidently.

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 only 40%, and the description names 'author and slug' while the schema actually exposes 'who', 'npub', and an undocumented 'd' — no slug parameter exists. The one sentence of mapping is therefore ambiguous and partially mismatched with the real parameter names, so it does not compensate for the coverage gap.

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 conveys that this fetches a single paper, either by id or by author+slug, and enumerates the payload (abstract, decision, revealed reviews). However, it never distinguishes itself from the sibling read_paper (or list_papers), and the trailing phrase 'read endpoint' is cryptic rather than informative.

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 versus read_paper, list_papers, or search. It also does not say which parameter combination (id vs who+npub vs d) selects which lookup mode, leaving the agent to infer routing from the schema alone.

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