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

No annotations are provided, so the description carries the full behavioral burden, yet "Battle" discloses nothing — not whether the call is read-only, what happens on an unknown id, whether the data is live or historical, or what shape the response takes. There is no annotation contradiction, but there is also no transparency.

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?

One word is technically concise but is under-specification rather than efficient communication; there is no front-loaded statement of action or scope for the agent to anchor on.

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 annotations, no output schema, and three parameters (one undocumented), the description should be doing substantial work — but it supplies nothing beyond the tool's subject matter. An agent cannot tell what this returns or how it differs from the replay sibling.

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 67%: id (19-digit arenaUniqueID string) and region (enum) are well documented in the schema, but language has no description anywhere. The description adds nothing beyond the schema, so it does not compensate for the remaining gap.

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 is the single noun "Battle", which merely restates the resource implied by the tool name battles_by_id. It names no verb and no retrieval behavior, so the agent must infer from the name alone that this fetches a single battle record by its id.

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?

No guidance is given on when to use this tool versus the obvious sibling battles_by_id_replay, nor on when a battle lookup is appropriate at all. The agent gets no conditions, prerequisites, or exclusions from the description.

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