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

Goes well beyond the readOnly/idempotent annotations: it declares cost ("FREE", "No payment required"), determinism ("arithmetic — never an opinion"), failure semantics ("a refusal is not experience", "an explicit null with a blocker"), and the pricing guarantee that the listed price is what will be charged. That is exactly the behavioral context annotations cannot carry.

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 key value proposition ("WHAT EARNS THE MOST XP NEXT") is front-loaded and each clause carries a distinct rule. The single long paragraph of semicolon-chained prohibitions is dense and could be split into bullets for faster scanning.

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?

Covers the response shape (per-item executable target or explicit null with blocker), the wait path, the auxiliary outputs (agent-track declaration, XP still available this window), and cost. With an output schema present, nothing an agent needs before calling is missing.

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?

Only one parameter, payer, and the schema has 0% description coverage, so the description must compensate. "Name your payer address" does clarify that payer is a wallet address, but gives no format, chain, or case example — minimal compensation for an undocumented required field.

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?

Names a specific outcome ("the OPEN quests for your wallet ranked deterministically by their XP reward and how little remains") with concrete follow-on fields. It never references the closest sibling, tollbridge_arena_quests, so an agent must infer the distinction between a ranked recommendation feed and a plain quest listing.

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 explicit operating context: "If action is wait, sleep until window_end; do not run a decision while a window is in progress; do not re-run a question to farm experience." These are clear when/when-not rules for acting on the result, though it does not route the agent to or away from any specific sibling tool.

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