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: no read/write nature, no batching or rate-limit behavior despite accepting up to 100 items per field, no auth requirements, no return shape.

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 words is under-specification rather than conciseness; there is no front-loaded detail to be concise about. It cannot be trimmed because there is nothing there.

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 a 4-parameter, multi-entity lookup tool with no annotations and no output schema, the description is wholly inadequate. An agent knows only that it needs a region and some ids/tags, not what it receives back or when to choose it over search_resolve.

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 100% (tags, clans, players, region all documented with formats and limits, with region enum), so the schema does the heavy lifting and the baseline of 3 applies. The description adds nothing about how the parameters combine.

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?

"Resolve a roster" essentially restates the tool name (resolve) plus a vague object. It never says what resolving means (id lookup? normalization? batch entity expansion?) or what a "roster" is, so an agent cannot distinguish it from the sibling search_resolve.

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, no prerequisites, and no mention of the obvious alternative search_resolve. The agent must infer entirely from the schema which case this tool serves.

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