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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only safety profile is covered structurally. The description usefully discloses the return composition (cover, hero, categorized photos with category and size), adding context beyond the annotations, though it says nothing about pagination or rate limits.

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?

A single front-loaded sentence that conveys scope and the sibling cap without waste. The parenthetical enumeration is dense but earns its place by clarifying what 'every photo' includes.

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?

With an output schema handling return values, annotations covering safety, and full parameter coverage, the description is nearly complete. It only omits return-count or pagination behavior, which the output schema likely covers.

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 lang, country, and place_id are fully documented in the schema itself. The description adds no syntax, format, or default details beyond what the schema already provides, so baseline 3 applies.

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?

States a specific verb+resource: returns every photo Apple Maps carries for a place, enumerating cover, hero, and categorized photos. It distinguishes itself from the sibling apple_maps_place by noting that 'the place tool caps at 20,' which signals the difference in scope.

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 'caps at 20' remark implicitly tells the agent to reach for this tool when it wants more than the place tool's limited photo set, but there is no explicit 'use this when' instruction or named alternative. Usage is implied rather than stated.

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