gbp_list_media

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that media items are listed and provides no information about pagination, authentication, ordering, filtering, or what happens when the parent location is invalid.

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 a single focused sentence with no filler. The verb and primary object are front-loaded, making it easy to scan and understand.

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?

The tool is relatively simple, and the parameter names (parent, pageSize, pageToken) are somewhat self-explanatory. However, with no annotations, no output schema, and only 33% schema coverage, the description leaves pagination behavior and return format to inference.

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 only 33%, with pageSize and pageToken lacking descriptions in the schema. The description adds minimal context for parent ('for a GBP location') but does not compensate for the undocumented parameters or clarify their expected values.

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 names a specific verb ('Lists'), the resource ('media items'), the content type ('photos, videos'), and the scope ('for a GBP location'). It is clear and distinguishes this from related tools like gbp_list_posts, though it does not explicitly name the sibling it is not.

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?

No guidance is given on when to use this tool versus alternatives such as gbp_list_posts or gbp_upload_media. There is no mention of prerequisites, exclusions, or context that would help an agent decide between similar GBP tools.

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