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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the tool is restricted to GMs, and it discloses the shape of the payload (order, current turn, round, live health, log) in the absence of an output schema. It does not say what happens for a non-GM caller or for an invalid battle id, which keeps it below the top mark.

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?

It is short, but it opens with a bare noun list rather than stating what the tool does, and the trailing 'Returns: The battle.' restates the title without adding information. Tightening to one sentence with a verb and the GM restriction would lose nothing.

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, the description must carry return-value information, and it does partially by naming the fields in the battle payload. However 'Returns: The battle' is circular, and nothing covers authorization failure behavior or whether the log is complete or truncated, which matters for an agent deciding whether to call it.

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?

Both parameters are fully documented in the schema (campaign slug-or-id, battle id) at 100% coverage, so the baseline applies. The description adds no extra meaning about identifier formats, lookup failures, or how campaign and battle ids relate.

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 enumerates the specific contents returned (turn order, current turn, round, live health, log), which makes clear this reads the state of a single existing battle. It lacks an explicit verb and never distinguishes itself from nearby tools such as list_battles or get_combat_roster, so an agent must infer the read-single-battle intent from the title and field list.

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 only guidance is the access restriction 'GM only'. There is no statement of when to call this versus list_battles (which presumably enumerates battles) or get_combat_roster, and no mention of prerequisites such as an active battle being required.

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