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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description goes further by disclosing the return format (viewable CDN URLs, not filenames) and the token requirement. It stops short of describing ordering, counts, or behavior when a Stay has no photos, so it is strong but not exhaustive.

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?

Three tight sentences: purpose and scope first, followed by the sequencing guidance and the auth constraint. Every sentence adds information an agent would otherwise have to guess, and nothing is repeated from the annotations.

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?

With no output schema, the description correctly compensates by characterizing the return value as full CDN URLs and by covering the auth prerequisite and pre-mutation use case. Minor gaps remain around empty-result behavior and whether results are grouped by area, but an agent has enough to call it 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 description coverage is 100% and the single parameter is fully documented in-schema ('The Stay's EntryID (use getMyStays to find it)'), so the description adds only an indirect pointer to its own resource scope. Baseline 3 applies when the schema already carries parameter meaning.

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?

States a specific verb and resource ('Get every current photo for a Stay') and enumerates the areas covered (listing gallery, hero, workspace gallery, host), which clearly separates it from siblings like getMyStayDetail or getMyStayRooms. It also specifies the return form (full https:// CDN URLs rather than filenames), so an agent knows exactly what it gets.

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 instructs 'Call this before deleteStayPhoto or reorderStayPhotos to see current filenames,' naming the sibling tools and the sequencing condition that selects this tool. It adds the auth prerequisite (NOMADSTAYS_MCP_AGENT_TOKEN), leaving little to inference.

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