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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is fully covered. The description adds that it is a one-shot aggregate returning many sections, which is useful context beyond the annotations, but it does not describe size/cost or what the output schema returns. Moderate added value.

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 'START HERE' directive. The feature list is dense but every element is informative; slight looseness from the long noun pile.

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 does not need to explain return values; it still tells the agent this is a broad orientation call to be used before strategy work. Missing only explicit mention of which sibling to use for deeper drill-down.

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% with a default of BTC and an example list of assets; the description does not add syntax, but the schema fully documents the single optional parameter. Baseline 3 plus the implicit guidance that the asset scopes the orientation view.

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 description is a bundle of nouns (status, tops, regime, monsters, recipes) rather than a clear verb+resource statement. It conveys that this is an orientation/overview tool but the scope is a list of features rather than a single purpose, making it hard to distinguish from arena_snapshot or get_world_arena_facts by purpose alone.

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?

Explicitly says 'START HERE for agents' and 'Call this before inventing strategies', which is a clear ordering directive. It does not name an alternative or exclusion, but the sequencing instruction is unusually strong for this dimension.

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