Hiscores lookup

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the lookup falls back to the saved account when no name is given, which materially affects invocation. It says nothing, though, about cursor-based pagination or failure behavior.

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?

Two compact sentences, front-loaded with the use case and with the default-account fallback placed right after. No filler or restatement of the title.

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 read-only lookup with full schema coverage and no output schema, this covers purpose, returned data and the default-account behavior adequately. Minor gaps remain: it does not mention paging via cursor or how modes affect results.

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 name, mode (with enum) and cursor are all documented in the schema. The description's note about defaulting to the saved account lightly enriches the optional-name semantics, but adds nothing about mode or cursor beyond what the schema already states.

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?

States a specific verb-and-resource (lookup a player's hiscores) and enumerates the returned data categories: skill levels, XP, ranks, boss kill counts, clue scrolls, combat level. It does not explicitly distinguish itself from the close sibling get_player_progress, but the scope is unambiguous on its own.

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?

'Use for a player's hiscores' implies the usage context, and 'Defaults to the saved account' clarifies behavior when no player is supplied. However, it names no alternatives (e.g. get_player_progress) and gives no when-not guidance, leaving the agent to infer selection.

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