Google Maps Photos

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. It only says 'Fetch' which implies a non-destructive operation, but it does not disclose async execution behavior, rate limits, authentication needs, or how the 'async' and 'execution_mode' parameters affect the request. The description lacks any warning about potential long-running operations or pagination.

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 concise, front-loaded with the core action, and uses a bulleted list for use cases. Every sentence earns its place; there is no redundancy or filler.

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 the tool has 10 parameters and an output schema, the description provides a sufficient overview. The output schema and parameter descriptions cover the details, so the description's focus on use cases is appropriate. However, it could be more complete with a brief mention of async behavior or note that the query parameter accepts multiple places, but these are partially covered by schema descriptions.

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 coverage is 100%, so the baseline is 3. The description adds value by hinting at the 'tag' parameter through phrases like 'menu photo retrieval' and 'owner photo', which map to enum values (menu, by_owner). This gives contextual meaning beyond the schema's generic 'Optional photo filter tag.'

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 clearly states the tool 'Fetch Google Maps photos' and enumerates specific use cases (place photo extraction, menu photo retrieval, owner photo and latest photo analysis), which distinguishes it from sibling tools like google_maps_reviews. The verb and resource are specific and unambiguous.

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 'Best for' list gives clear context on when to use the tool (photo-related tasks) but does not explicitly mention alternatives or when not to use it. It implies differentiation from review/search tools but could be more explicit about exclusions, such as 'Use google_maps_reviews for reviews.'

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