Get Zillow property photo gallery

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint as true. The description adds valuable behavioral context: it is 'Read-only; safe to call repeatedly' and warns about token budget for large properties. No contradictions.

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, well-structured paragraph. It front-loads the purpose, provides essential parameter guidance, and adds warnings. Every sentence adds value with no fluff.

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?

Despite lacking an output schema, the description explicitly states the return format ({ zpid, count, photos, street_view_url?, high_res_url? }). It covers all parameters, usage constraints, and edge cases (token budget). Completely adequate for an agent to invoke correctly.

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 coverage is 100% with well-described parameters. The description adds significant value: explains that include_sources defaults to false but auto-enables for <~15 photos, and warns of token budget. This goes beyond the 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?

The description explicitly states the tool returns 'the full photo gallery for a Zillow property' with specific details about response structure (hero URL, jpeg/webp variants, caption). It clearly distinguishes from sibling tools (e.g., zillow_get_property) which handle different data.

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?

Provides clear usage instruction: 'Provide exactly one of zpid or url.' Warns about potential token budget issue with include_sources. However, it does not explicitly state when to avoid this tool in favor of siblings, though the purpose makes it obvious.

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