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

No annotations are provided, so the description must disclose behavior. It states that recommendations never shoot, move, or reveal hidden state, which is a strong safety guarantee. It also mentions the tool is free, but does not cover rate limits or error behavior, so it is not fully transparent.

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 concise with three sentences and front-loads the core purpose. It includes some non-essential metadata like '[FREE]' and 'inv #4275' that does not aid tool selection, but overall it is efficiently structured.

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?

An output schema exists, so return values are covered. The description provides usage context for policy_text and auth, but omits explanations for game and limit, and does not mention any preconditions or error scenarios, leaving gaps for a tool with five parameters.

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?

With 0% schema coverage, the description must explain parameters. It explains policy_text with an example and clarifies player_id/token for authentication. However, it leaves game and limit unexplained, which are still ambiguous to the agent.

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 a specific verb (rank) and resource (open tournament pots) and the method (combat-policy similarity). It also clarifies that the tool only provides recommendations and does not take actions, distinguishing it from action-oriented siblings.

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 two usage modes: sending policy_text or authenticating with player_id/token. However, it does not explicitly mention when to use this tool over alternatives like aiarena_tournament_suggestions, so it lacks exclusion guidance.

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