Google Maps Photos

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

The description is a single 'retrieve' statement and does not disclose behavioral traits such as identifier requirements, empty-result behavior, pagination, or read-only guarantees. Since no annotations are provided, the description carries the full burden of behavioral disclosure and falls short. It does not contradict any annotation, but it adds little beyond what the tool name already implies.

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, front-loaded sentence with no filler, repetition, or redundant phrasing. It is efficient and readable, though it sacrifices some behavioral and usage context for brevity. Every word earns its place.

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 read-only tool with a complete output schema and fully documented parameters, the one-sentence description is minimally viable: it names the resource and lets the schema handle invocation details. However, it lacks guidance for choosing among sibling photo/review/post tools and offers no behavioral caveats. An agent could likely call it correctly with placeId, but not optimally in all contexts.

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 five parameters are fully documented in the schema with 100% coverage, so the description does not need to repeat them. The description adds no extra meaning about how dataId, placeId, or categoryId interact, but the schema already provides that information. The baseline of 3 applies because the schema carries the parameter semantics.

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 ('Retrieve') and a concrete resource ('the photo feed for a place'), which clearly distinguishes it from sibling tools like google_maps_search, google_maps_reviews, and google_maps_posts. It does not explicitly state scope details like category filtering, but the schema covers that. Overall, an agent can tell what this tool does without opening the schema.

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 provides no guidance on when to use this tool versus alternatives such as google_maps_reviews, google_maps_posts, or google_maps_contributor_reviews. There are no exclusions, conditions, or hints about which sibling tool to choose for non-photo content. The only implied context is 'for a place,' which is too thin to route an agent reliably.

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