maps_open_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 disclosing side effects. It mentions that expectedLabel is 'revalidated immediately before exactly one bounded photo control is activated,' that 'the previous place semantic state is invalidated after the verified viewer transition,' and that 'Interactive Assist must be enabled.' These details explain preconditions and state changes, though the language is technical and cryptic (e.g., 'bounded photo control'), making it less accessible than ideal.

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 three sentences and front-loads the main purpose, which is good. However, the second and third sentences are dense with jargon ('revalidated immediately before exactly one bounded photo control is activated') that could be simplified for clarity. It is concise but not maximally understandable.

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 tool with one required parameter and no output schema, the description should fully explain what the parameter is and how the tool behaves. It lacks a clear definition of expectedLabel and does not describe the expected return value or effect beyond 'opens viewer.' The mention of state invalidation and Interactive Assist adds context, but the missing parameter semantics makes it incomplete.

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 schema has zero description coverage, so the description must clarify the expectedLabel parameter. It only states that expectedLabel is required and revalidated, but does not explain what the label should represent or how to obtain it. This leaves the agent guessing about the correct value, which is insufficient for a single-parameter tool.

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 action: 'Open the visible Google Maps photo viewer for the currently selected place.' This gives a specific verb and resource, and the phrase 'for the currently selected place' distinguishes it from other map tools like search or directions. However, it does not explicitly mention sibling tools or contrast its scope, so it earns a 4 rather than a 5.

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. It mentions a prerequisite ('Interactive Assist must be enabled') but does not discuss exclusions or situations where other tools (e.g., maps_show, maps_select_result) would be more appropriate. This leaves the agent without clear selection criteria.

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