google_map_place_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 and does so thoroughly. It reveals the source of imagery, entry contents (URL plus pixel dimensions), how to resize via URL suffix, exclusions, lack of pagination, and the 1 request/second rate limit.

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 compact yet information-dense: every sentence adds value, from purpose to file format details, exclusions, pagination status, and rate limiting. The main clause appears first, giving immediate clarity.

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?

Despite lacking annotations and an output schema, the description provides enough context for an agent to invoke the tool correctly: required place_id, optional limit semantics, return entry contents, URL transformation behavior, exclusions, and rate limit. This is a complete picture for a 2-parameter read tool.

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?

The input schema already documents both parameters with 100% coverage, so the baseline applies. The description reinforces that place_id identifies the place and mentions output URL sizing, but it does not add materially new meaning to the parameters themselves.

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 opens with a specific verb and resource: 'Returns the photos Google publishes for a specified place_id' and clearly scopes it to the place page's image set. It differentiates from sibling tools by explicitly excluding contributor avatars and review-attached photos, and from archive-type feeds by noting it is 'not a paginated archive feed.'

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 makes the intended use clear: retrieve place photos for a Google Maps place_id. It also gives context around what is excluded and the one-request-per-second rate limit. However, it does not explicitly name alternative sibling tools or state 'use X instead when...', so it falls short of a 5.

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