get_photos

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to restate safety. It adds value by disclosing the return fields (URLs, captions, sort order) and the scope of the fetch (specific listing), which helps the agent understand what to expect beyond the 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 a single concise sentence that is front-loaded with the verb 'Fetch' and immediately identifies the resource. It includes essential output hints without any waste, making it highly efficient.

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 (one parameter, no nested objects) and no output schema, the description sufficiently covers what the tool returns (URLs, captions, sort order) and the input needed. This is complete for an agent to invoke the tool correctly and understand the result.

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 fully describes the only parameter 'listingId' with its description. The description's phrase 'specific listing' reinforces the parameter's purpose but doesn't add new semantic details beyond the schema. Thus, the baseline score of 3 applies, as the schema carries the burden.

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 clearly states the verb 'Fetch' and the resource 'photos for a specific listing', and lists specific fields (URLs, captions, sort order). It distinguishes well from sibling tools like get_listing and update_photos by focusing solely on the photo retrieval use case.

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 context for when to use the tool: whenever you need photos for a listing, including their URLs, captions, and sort order. It doesn't explicitly mention alternatives or exclusions, but the scope is unambiguous and sufficient for most AI agents to select it correctly.

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