Get Compass property photo gallery

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

The description adds meaningful behavioral context beyond the readOnlyHint/idempotentHint annotations: sha-only calls fetch a view that redirects, default category filtering is 0, and non-photo media can be included via a flag. It also confirms the return shape and that the tool is safe to repeat, matching the annotations without contradiction.

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?

Every sentence earns its place: purpose first, then result contents, then parameter alternatives, then default/filter behavior, then return shape. The description is compact yet information-dense with no filler.

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 tool with no output schema, the description is complete: it covers the returned object shape, image URL fields, parameter alternatives and defaults, and the redirect behavior. Nothing needed to call the tool correctly is missing.

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 already covers all three parameters with descriptions, so the baseline is 3. The description adds extra value by explaining the relationship between `url` and `listing_id_sha`, the internal redirect behavior for sha-only calls, and the meaning of category 0 in the default filter.

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 states a specific verb and resource: 'The full photo gallery for a Compass listing — every image in listing.media[]'. This clearly differentiates from sibling tools like compass_get_property or compass_search_properties, which serve broader property/search purposes.

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 clear invocation details, such as passing either `url` or `listing_id_sha` and the `include_all_categories` option. However, it does not explicitly state when to choose this tool over siblings like compass_get_property or when not to use it, so usage guidance is implied rather than explicit.

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