Get listing photos

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

Annotations already mark this as read-only and open-world, so safety is covered. The description adds useful behavioral context beyond the annotations: approximate image sizes ('~28KB each'), the fact that images are returned inline, and that CDN fetches are fast with no politeness delay needed. These are concrete behavioral details not present in the schema or annotations.

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 two sentences with no filler. The primary purpose is front-loaded, followed by key operational details about image size and fetch speed. Every sentence adds valuable information, and the structure allows an agent to quickly understand both purpose and constraints.

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?

Given the tool's low complexity, a rich output schema, and read-only annotations, the description is complete enough for an agent to select and invoke it correctly. It covers purpose, visual inspection use case, payload size considerations, and speed expectations. The presence of an output schema means the description does not need to detail return structure.

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 the schema already documents id, size, and maxPhotos meaningfully. The description добавляет minimal parameter-specific value beyond repeating the 'Large' size and image size. It gives the high-level purpose for the return data but does not need to, because the schema already covers parameter meanings.

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: 'Fetch a listing's photos as inline images.' The stated purpose of inspecting condition and authenticity cues makes it clear this is a visual inspection tool, distinguishing it from sibling search and watch-info tools. The singular 'listing' scope differentiates it from broader listing-related operations.

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 gives clear context for when to use this tool: when a listing's photos need to be visually inspected for condition and authenticity cues. It also adds operational guidance, noting 'Fast CDN fetches (no politeness delay needed),' which helps the agent plan calls efficiently. It does not explicitly state when not to use it or name alternatives, but the context is clear.

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