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

No annotations are provided, and the description contains no behavioral information whatsoever—no side effects, permissions, rate limits, or output characteristics. The description fails to disclose any trait beyond the tool's name, which is especially problematic because the burden is entirely on the description.

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?

The description is short but under-specified, which is not the same as being concise. A single versioned name phrase provides no structured information, no front-loaded key details, and no useful content, making it an inadequate description rather than a model of brevity.

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?

Given this tool has 4 parameters, no annotations, no output schema, and three sibling tools, the description is entirely inadequate. It omits information about how to invoke the tool, what inputs are expected, what outputs look like, and how it relates to maps_jobs, maps_results, and maps_status, so an agent has no basis for correct invocation.

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?

All four parameters (lang, depth, email, query) are undocumented in the schema (0% coverage), and the description provides no explanation of them. The description does not compensate for the schema's lack of parameter descriptions, leaving the agent without any semantic understanding of inputs.

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 'V1 Maps Search' essentially restates the tool name, with 'V1' being a version marker and 'Maps Search' a noun phrase echoing 'maps_search'. It does not specify what the tool does, what resource it acts on, or how it differs from sibling tools, and it fails to articulate a clear purpose beyond a label.

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?

The description gives no guidance on when to use this tool versus alternatives such as maps_jobs, maps_results, or maps_status. No use cases, prerequisites, or exclusions are mentioned, leaving the agent without any basis for tool selection.

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