Get Player Stats

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

Annotations only indicate readOnlyHint=true. The description adds valuable behavioral context: that normal mode works via Jagex index_lite, and that ironman/hardcore endpoints are currently broken (HTTP 404), with the tool explicitly reporting this rather than silently falling back to normal data. This goes beyond the annotation and helps the agent understand failure modes.

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 two sentences and front-loaded with the main purpose, followed by a clear caveat about ironman/hardcore endpoints. Every sentence earns its place; there is no fluff.

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 simple lookup tool with only 2 parameters and no output schema, the description covers the core behavior and an important limitation. It doesn't describe the shape of the hiscores response, but given the lack of output schema and the tool's simplicity, it is reasonably complete. Minor gap: no mention of error handling beyond the 404 case.

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 schema already covers both parameters (username and gameMode) with descriptions, so the baseline is 3. The description adds semantics for the gameMode parameter by explaining the behavior for normal vs ironman/hardcore, which is not in the schema. This extra context justifies a 4.

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 states the tool's purpose: 'Get RS3 hiscores for a player.' It uses a specific verb and resource, and immediately distinguishes itself from sibling tools (which are all item/price related). The mention of normal vs ironman/hardcore modes further clarifies scope.

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?

The description provides context about when the tool works as expected: normal mode uses index_lite, while ironman/hardcore modes currently return 404 and the tool reports this clearly. This tells the agent what to expect for different game modes, though it does not explicitly reference alternative tools since none exist in the sibling list.

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