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

With no annotations provided, the description carries the disclosure burden. It adds useful behavioral context: the operation is a fetch (read-only), the result is paginated JSON, and output respects user export column preferences. It does not disclose behavior for incomplete jobs, error conditions, or pagination termination, but it offers more than a bare verb.

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?

A single sentence that front-loads the action and resource, then adds the two most decision-relevant constraints: pagination and user column preferences. Every clause earns its place with no redundant wording.

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 simple 3-parameter paginated fetch with no output schema, the description covers the core lifecycle precondition, the output format, and a behavior that affects result shape. It would be marginally stronger if it pointed to gmaps_get_job for checking completion, but the tool is adequately specified 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?

Schema description coverage is 100%, so the schema already explains jobId, limit, and cursor. The description adds only general context ('paginated', 'respects user export column preferences') rather than parameter-specific semantics, which is acceptable but not additive beyond the schema baseline.

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 names a specific verb ('Fetch'), a specific resource ('paginated place rows as JSON'), and a lifecycle condition ('for a finished maps job'). It also distinguishes this tool from siblings like gmaps_get_photos_results and gmaps_get_reviews_results by scoping to 'place rows', and from gmaps_get_job by scoping to results rather than job 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?

The phrase 'for a finished maps job' gives a clear precondition and implies this is the results-retrieval step after job completion. However, it does not explicitly state when not to use it, nor does it name alternatives such as gmaps_get_photos_results or gmaps_get_reviews_results for non-place results.

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