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

With no annotations, the description carries the full burden. It discloses the paid entry cost, the queueing action, and the possible return states (queued or matched with match_id and mark). It does not mention side effects beyond payment, such as whether the queue entry can be cancelled or expires.

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-loaded: it starts with the mandatory payment, states the action, summarizes return values, and lists next steps. Every sentence adds useful information with no wasted words.

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 tool with one simple parameter and an output schema, the description covers action, cost, return semantics, and workflow. The main gap is the undocumented player_token parameter, plus vague preconditions around registration and payment readiness.

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 only parameter, player_token, has no schema description and 0% schema description coverage. The tool description never mentions player_token, so an agent is left to infer its format, purpose, and source. A self-explanatory name helps slightly but does not make up for the missing documentation.

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 states the action: queue a SHADOW COMMAND agent for a live match, with a specific verb and resource. It does not explicitly name the generic sibling aiarena_queue, but 'SHADOW COMMAND agent' narrows the scope and helps distinguish it.

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 provides a clear follow-up workflow: queue first, then read match state, then move. It does not explicitly explain when to choose this tool over alternatives or mention exclusions, so usage guidance is implied rather than fully specified.

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