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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed world), and the description adds real context on top: page size cap ('at most 12 photos'), no-dates-required, and the scoping invariant that a room never includes property photos. It stops short of return format or error behavior, but that is acceptable given 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?

Front-loads the key data-only vs. rendered distinction and is dense with operational rules. The closing sentence restates the data-only/render contrast already made in sentence one, a small 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?

An output schema exists, so return values need no explanation, and the description covers usage routing, view defaulting, room scoping, and page size. Missing detail on offset/roomQuery semantics is the only real gap for a 5-parameter paginated tool.

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?

With schema coverage at 40%, the description does useful work on roomId ('exact room IDs from availability or a unique room name; no substitutions') and on view defaulting, but offset and roomQuery are left unexplained in both the schema and the description. Adequate compensation, not complete.

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 ('read a page inside an already mounted gallery') and immediately scopes it against the sibling show_property_photos. An agent can distinguish it from the other photo-listing tools without opening a schema.

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 names when to use the alternative ('For initial presentation use show_property_photos') and even states a prohibition ('do not page this tool to assemble Markdown image grids'). It also gives the default selection rule between PROPERTY and ROOM, leaving nothing to inference.

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