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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), and the description meaningfully adds context: it reads Everloot's authorized public corpus when connected, reports missing data explicitly, and warns that the gold difference is not an accusation. This is substantive behavioral disclosure beyond the annotations.

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 a chain of terse, cryptic sentences ('Gameplay stays on its own line', 'A missing line is unrecorded') that read as stream-of-consciousness. The first sentence is front-loaded, but the rest is opaque rather than economical.

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?

An output schema exists, so return structure need not be explained, and the description covers several behavioral caveats. Still, the meaning of the 'money line' / 'own line' distinction is unclear, leaving an agent unable to fully predict what the ledger contains.

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% for both required parameters (realm, character), so the schema carries the parameter burden. The description adds no syntax or format detail for character/realm, consistent with a baseline 3.

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 opening sentence states a concrete resource: peak gold plus the money events from a character's own upload. However, the following jargon-heavy sentences ('money line', 'its own line') muddy what the tool actually returns and never differentiate it from siblings like auction_history or market_value.

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 lists constraints ('no scan of a player who did not upload', 'installs are not merged') but never states when to prefer this tool over alternatives such as auction_history. No explicit when/when-not routing is present.

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