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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral context beyond annotations: the data is paper-trading and 'not a verdict,' which warns the agent about its epistemic status. It does not detail return shape, but an output schema exists.

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 compact and front-loads the core purpose before listing contents and sequencing. The list is dense but each item conveys scope; nothing is obviously wasteful, though the phrasing is closer to a checklist than a polished explanation.

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?

Given the output schema, annotations, and single well-documented parameter, the description supplies enough context for an agent to know what the tool aggregates, when to call it, and that its data is paper-trading. It could be more explicit about the asset parameter's effect, but overall it is complete enough for correct invocation.

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%, and the single asset parameter is documented in the schema with its default and examples. The description does not add meaning about how asset affects the orientation output, so the baseline 3 is appropriate.

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 clearly identifies this as a one-shot arena orientation and enumerates the domains it covers: live status, multi-asset tops, regime, monsters, community pulse, templates count, and play recipes. It distinguishes its aggregate scope from prerequisite tools like get_product_contract and get_public_proofs, though it does not explicitly contrast with sibling tools such as market_regime or 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?

It gives explicit sequencing: call after get_product_contract and get_public_proofs, and before inventing strategies. That is strong when-to-use guidance. It does not state when not to use it or name alternative tools for specific sub-tasks.

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