start_battle

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

Without annotations, the description provides a detailed flow: navigate -> prepareBattle (auto-selects best books) -> wait for BattleSetting -> startBattle -> wait for Battle. It also explains the auto-selection criteria and override capability.

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 two paragraphs. The first sentence front-loads the main purpose, and subsequent sentences add detail without redundancy.

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?

Given the presence of an output schema, the description is fully complete: it explains the flow, parameters, and auto-selection logic, leaving no gaps for an AI agent.

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 coverage is 100%, and the description adds significant meaning: explains the auto-selection logic (composite score of HP, breakLife, resistances) and clarifies when to use book_ids, going beyond the schema.

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 tool's purpose: 'Start a battle for the given stage with automatic book selection.' It uses specific verbs and distinguishes from siblings like battle_loop and play_round.

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 explains when to use explicit book_ids (high-difficulty stages) but does not explicitly compare to sibling tools or state when not to use this tool.

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