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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description usefully adds the authorization requirement ('Requires mcp:write'), which is not in the annotations. However, it says nothing about why a create operation is flagged destructive, whether the battle persists, or what confirmation/response behavior to expect.

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?

Two tight, front-loaded sentences with no padding; the create action and the auth requirement lead. The clause 'using the same rules as the site' is vague enough to consume space without adding actionable meaning.

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 an 8-parameter mutation tool with no output schema and zero schema descriptions, the description is far too thin. An agent cannot reliably populate casual, manual, limit, or the opponent/ally id variants from what is given, and no result shape or validation constraints are conveyed.

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% across 8 parameters, so the description carries the full burden and mostly fails it. 'Named player seats' loosely gestures at guestNames/opponentIds, but limit, casual, manual, allyId, opponentId and missionPackId are entirely unexplained and the distinction between opponentId and opponentIds goes unaddressed.

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 a specific verb and resource ('Creates a battle') plus a scoping detail ('with named player seats'), which an agent can separate from submit_battle_action and get_my_battle. It stops short of naming any sibling or clarifying how it differs from simulate_combat or list_my_battles.

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?

There is no when-to-use guidance and no mention of alternatives, despite a crowded sibling set containing simulate_combat and submit_battle_action. The only routing signal is the prerequisite 'Requires mcp:write', which tells the agent whether it is authorized but not when this tool is the right choice.

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