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 indication that 'q' is a prefix match, that region is mandatory, what the result shape or ordering is, or whether pagination/limits apply. For a search tool with zero structured behavioral hints this is a complete gap.

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 with no waste, but this is under-specification rather than conciseness. There is no front-loaded scope, result expectation, or constraint to anchor the agent.

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, no annotations, two required parameters, and a two-word description, an agent cannot tell what a call returns or how the prefix search behaves. The description is far too thin for the tool's contract.

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% — 'q' is documented as "Search prefix" and region as a three-value enum — so the schema already does the heavy lifting. The description adds nothing on top, which makes the baseline 3 appropriate.

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?

"Search maps" restates the tool name maps_search almost verbatim, so it is effectively a tautology. It does convey a verb and resource, but it does not distinguish this tool from siblings such as maps, maps_search_ndjson, or the parallel tanks_search/players_search/clans_search family. An agent learns nothing about scope (e.g. prefix search) beyond the name.

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 exclusions, and no mention of the alternative maps_search_ndjson or the plain maps endpoint. Nothing signals whether this is the right entry point for looking up a map by name or what to do with the results.

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