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

Annotations already declare readOnly/idempotent/openWorld, but the description adds real value: progress is derived from an append-only XP journal with 'no separate counter,' and it preempts the natural confusion that a required 'payer' implies payment by stating 'No payment required.' That resolves a non-obvious behavioral trap.

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-loads the key framing ('FREE — THE QUEST BOARD') and the rest is informational. Slightly wasteful in repeating the no-cost point twice ('FREE' and 'No payment required'), but overall tight for the amount of detail conveyed.

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, the description need not explain return shape, and annotations cover the safety profile. It gives the agent the framing (free, journal-derived progress, required payer) needed to call it correctly, missing only explicit sibling routing.

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 0% and the single 'payer' parameter is undocumented in the schema, so the description carries the burden. It clarifies that 'payer' is an address to name and is not a payment trigger, which is more than the schema provides, though it does not state the address format.

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 ('the daily and weekly quests with your live progress') and what each entry contains, so the agent knows exactly what comes back. It reads clearly as the quest-board retrieval tool, though it never explicitly contrasts itself with near-siblings like tollbridge_arena_next_action or tollbridge_arena_leaderboard.

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?

Usage is only implied: 'Complete one to bank its XP toward your next rank' hints at why an agent would fetch the board, but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool. Adequate but leaves the agent to infer routing.

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