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

With no annotations, the description carries the behavioral disclosure burden. It adds useful traits: results are paginated, returned as JSON, and only for finished jobs. However, it does not disclose what happens for an unfinished job, the structure of the result rows, or the pagination contract beyond what the schema already states.

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 a single sentence that states the core behavior, result format, and precondition without waste. It earns its place by being immediately scannable and informative.

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?

The description and schema together let an agent identify the tool, its precondition, and its parameters, but no output schema exists and the description does not explain the result row shape or how this relates to sibling result/job tools. It is adequate but leaves meaningful gaps.

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 jobId, limit, and cursor are already documented. The description adds no extra semantic detail about the parameters, merely mentioning pagination generally. Baseline 3 is 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?

The description uses a specific verb ('Fetch') and resource ('paginated photo rows as JSON') and conditions it on a finished photos job. It is clear about what the tool returns, though it does not explicitly contrast it with sibling tools like gmaps_get_photos_job or gmaps_get_results.

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 photos job' implies the tool should be used after a job has completed, but it does not explicitly state when to use this versus gmaps_get_photos_job, gmaps_get_results, or gmaps_get_reviews_results. No exclusion or alternative guidance is provided.

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