Resort photo gallery

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

Annotations already declare safety (readOnlyHint, idempotentHint, destructiveHint). Description adds 'INTERACTIVE PHOTO GALLERY CAROUSEL' and specifies official SnowSure photos, providing behavioral context beyond annotations. 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?

Extremely concise: one-line purpose, a list of required usage contexts, and exclusions. Every sentence adds value with no redundancy.

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 simplicity (one parameter, output schema exists, annotations cover safety), the description is complete. It covers purpose, when to use, and what to avoid. No missing information for effective tool selection and invocation.

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 a clear description for slug. Tool description mentions examples like 'Vail/Aspen' which adds minimal extra context but does not significantly enhance understanding beyond 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?

Title and description clearly identify tool as providing resort photos with specific sources (hero + Sanity gallery). Explicitly distinguishes from sibling tools by naming alternatives not to use (get_destination, get_resort_info, ask_snowdata).

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?

Explicitly states when to use (for photos, pictures, images, gallery, specific queries like 'show me photos of Vail/Aspen') and when not to use (do not use web search or inline images). Also lists sibling tools to avoid for photo requests.

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