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, and it discloses nothing: not whether the feed is incremental, time-windowed, or paginated, not what a 'change' contains, and not whether it is a read-only operation. 'Feed' hints at changelog semantics but conveys no actionable behavior.

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?

Three words is not conciseness but under-specification; there is no front-loaded statement of purpose, no scope, and no return expectations. Brevity here costs the agent more than it saves.

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 and no output schema, the description is the only source of behavioral context, and it supplies none. For a 'changes feed' the agent needs to know the change window, whether results are incremental, and the response shape — all absent.

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?

Only one parameter exists and the schema documents it fully (100% coverage) with an enum of eu/na/asia and the description 'Game server region.' The tool description adds nothing beyond this, which is the expected baseline when the schema does the heavy lifting.

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?

"Tank changes feed" is essentially the tool name restated. It implies a changelog/delta stream for tanks but names no specific operation (list? poll? subscribe?) and does not distinguish it from siblings like tanks_by_slug_history or maps_changes, which follow the same naming pattern.

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 guidance on when to use this tool versus alternatives. An agent cannot tell whether this is for discovering recently added/modified tanks, polling for updates, or something else, nor how it relates to tanks, tanks_search, or tanks_by_slug_history.

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