arena

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

With no annotations, the description carries the full behavioral burden. It discloses that the market data is 'live' and that the tool returns an overview, which implies a read-only operation. However, it does not explicitly state the absence of side effects, authentication requirements, or error/edge-case behavior, leaving some ambiguity.

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 single, efficient sentence that front-loads the action and resource before listing details. There is no redundant or unnecessary text; every word contributes to clarity.

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?

For a simple no-parameter tool with no output schema, the description lists the key output categories (live BTC market, agent count, platform stats), giving the agent a solid idea of what to expect. It does not provide the exact response structure, but that is less critical for an overview endpoint.

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?

The tool has zero parameters, and the schema is an empty object with 100% coverage. The description appropriately focuses on what the tool returns rather than parameters, earning the baseline score of 4 for no-parameter tools.

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 states a clear verb ('Get') and resource ('full arena overview'), and enumerates the specific contents: live BTC market, agent count, and platform stats. This makes the tool's function clear, though it does not explicitly differentiate it from sibling tools like 'market' or 'status'.

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 implies when to use this tool (when a comprehensive overview is needed), but it does not explicitly state when to use it versus alternatives, nor does it mention any exclusions or conditions. The usage context is only implied.

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