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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one piece of context beyond that (these are profile-level photos, not post media). It says nothing about pagination behavior or result ordering, but with annotations carrying the safety burden a 3 is appropriate.

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?

Two short sentences with zero filler, and the core operation is front-loaded ahead of the disambiguating nuance. Every sentence 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 list tool with a fully documented parameter schema and no output schema, the description covers what it is and how it differs from post media. Pagination and return-shape details are the only omissions, and the schema already hints at pagination, so it is adequate.

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 description coverage is 100%, so page_size, page_token, profile_id, and location_id are already documented in the schema. The description adds no parameter-level detail (e.g., how to obtain location_id or how page_token chains). Baseline 3 for a fully-documented schema.

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 and resource: 'List the photos and videos on a Google Business Profile location.' It adds a useful scope clarification that these are profile photos rather than media attached to a local post, which helps distinguish it from other media concepts. It doesn't explicitly differentiate from the closer siblings media_create/media_delete, but the verb makes the distinction obvious.

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 second sentence implies the usage boundary by contrasting profile media with local-post media, which helps an agent route correctly. However, there is no explicit 'use this when' statement, no alternatives named, and no mention of prerequisites or pagination workflow. Usage is only implied.

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