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

Goes well beyond the readOnly/destructive annotations by disclosing the trust model: an entry is public only after 3 installs report it identically, and progress appears only when the install uploaded with the collection-sharing choice plus a verified grant, otherwise the answer says so. This is exactly the kind of authorization, aggregation, and data-availability context an agent needs before promising results.

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?

Front-loaded with what the tool returns, then the trust/availability caveats, then scope exclusions — a sensible order with no filler sentences. It is dense and slightly repetitive in re-stating the corpus and 'not a copied catalog' idea, which keeps it short of a 5.

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 an output schema present, return values need no explanation, and the description adequately covers authorization prerequisites and data-availability behavior. It leaves the relationship to sibling tools like collection_gap or quest_page unstated, which is the main remaining gap for an agent choosing between them.

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 100%, so both parameters are already documented in the schema. The description adds only indirect framing ('one install's characters', install-uploaded data) and no syntax, format, or interaction details beyond what the schema provides, so the baseline 3 applies.

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 resource (one install's characters' completion data) broken into concrete categories — achievements ranked by criteria met, reputations near next standing, titles known, quests finished in a chain. It explicitly distinguishes itself from adjacent concepts ('Not a Blizzard profile read and not a copied catalog'), so an agent can route away from profile-style reads and catalog lookups.

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?

Gives clear context: it reads Everloot's current authorized public corpus when connected, and states that missing or unavailable data is reported explicitly rather than silently. It does not name a sibling alternative (e.g. collection_gap or quest_page) for when a narrower query is preferable, so the when-to-use-vs-alternative guidance is implied rather than explicit.

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