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. "Streamed" is the only behavioral hint and it is left unexplained: no indication of the output format, chunking/ordering guarantees, rate limits, or auth requirements for what appears to be a streaming search endpoint.

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?

Only three words with zero padding and the core action front-loaded, but the brevity tips into under-specification for a tool with required parameters and a non-obvious streaming behavior. It reads as terse rather than efficiently concise.

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 and no annotations, the description is the only place streaming semantics, output framing, and sibling differentiation could live, and it supplies none of them. An agent would have to guess when this tool is preferable to maps_search.

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% with only two parameters (q as "Search prefix" and region as an enum), so the schema fully documents the inputs. The description adds no syntax or format detail beyond the schema, making 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" gives a specific verb+resource, and "(streamed)" hints at a distinction from the sibling maps_search. However, the parenthetical is ambiguous about what streaming actually means, so an agent cannot confidently tell the two search variants apart.

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 mention of the sibling maps_search as an alternative, and no condition that would select the NDJSON variant over the regular one. Usage must be inferred entirely from the name.

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