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

Adds real context beyond the annotations: it requires the caller's api_key, is private and unranked, and is paper-trading only. Annotations declare readOnlyHint=false without explanation, and the description does not contradict this — it simply describes a private data pull, leaving the read/write semantics of that flag unaddressed.

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 privacy and scope constraints are front-loaded in parentheses before the payload list, which is efficient. The trailing disclaimers ('Paper trading only. Not financial...') consume space without aiding tool selection.

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 no output schema and only two trivial parameters, the description fully carries the burden: it enumerates the returned fields, states the auth requirement, and clarifies visibility and ranking behavior. An agent knows what it will get back.

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 0%, so the description must compensate; it explains that api_key identifies the bot ('needs its api_key'), but says nothing about agent_id, which is equally required. Partial compensation for a two-parameter tool.

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 the specific resource — the caller's own bot status — and enumerates the payload: orders in the last 7 days, duplicate-copy detection, and a 3-line briefing. That level of detail distinguishes it from generic siblings like arena_check or arena_info, though it never names a sibling to sharpen the boundary.

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?

'Good first call on a return visit' gives one concrete usage context, and 'never public, never ranked' hints at scope. But there is no explicit when-not guidance and no reference to arena_check, arena_pnl, or arena_points, which an agent would need to choose between.

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