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

No annotations are provided, so the description carries the full burden, and it discloses nothing: not the ordering assumption, tie handling, input format (comma-separated? JSON array?), numeric coercion, or error behavior for out-of-range n. It is behaviorally opaque.

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 short, but this is under-specification rather than conciseness. The single redundant repetition of the name earns no place and conveys no information.

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 two-parameter numeric tool with no annotations and no output schema, the description supplies zero of the needed context: input encoding, rank semantics, tie/duplicate handling, and edge cases are all absent.

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 100%, so the baseline is 3; the schema itself only says "N to process" and "Values to process", but the tool name plus description implies n is the rank and values is the source list. That modest inference adds a little meaning over the tautological schema text without fully compensating.

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 is the tool name restated: "Nth Largest: Nth Largest". It is a pure tautology with no verb, resource, or scope articulated beyond the name itself, and it does not distinguish itself from the sibling x402-nth-smallest.

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 when-to-use guidance, no prerequisite, and no mention of the obvious alternative (x402-nth-smallest) or of related statistics tools. Nothing tells an agent under what conditions to pick this tool.

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