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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it says nothing about return values, side effects, pagination, authentication, or the source of the 'results.' The word 'Results' weakly implies a read operation, but no actual behavior is disclosed.

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 under-specification, not conciseness. There is no front-loaded meaning, no sentence structure, and no attempt to convey the tool's function or constraints.

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 no output schema, no annotations, and two completely undocumented parameters, the tool is missing nearly all context an agent needs. The description is a placeholder and does not sufficiently describe what the tool does or how to invoke it correctly.

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 0%, and the description does not mention 'limit' or 'job_id' at all. An agent cannot infer what these parameters control, how they interact, or whether job_id refers to a maps job from a sibling tool.

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 Results' is a bare noun phrase with no verb and essentially restates the tool name. It does not indicate an operation such as fetching, listing, or exporting, and it provides no differentiation from sibling tools like maps_jobs or maps_status.

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, what problem it solves, or how it relates to the sibling tools. The sibling names imply related workflows, but the description never mentions any selection criteria or exclusions.

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