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

Annotations already carry readOnly/openWorld/non-destructive, so the bar is lower. The description adds genuine value with the ordering guarantee ("Newest first as Street orders them") and pagination guidance, but says nothing about the response shape or that deleted/cancelled records are hidden unless the schema flags are set.

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?

Two short, front-loaded sentences with the ordering and paging facts placed early. The trailing "GET /viewings" is a minor piece of low-value filler but costs little.

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?

For a 14-parameter, filter-rich list tool with no output schema, the description is functional but thin: it never describes what the response envelope looks like or how the `include` embedding affects it. The schema compensates on parameters, but the response side is left entirely unexplained.

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% across all 14 parameters, including enum values, defaults, and date-time semantics, so the schema does the heavy lifting. The description only reiterates page/page_size and does not add filter semantics beyond what the schema states.

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?

Specific verb+resource ("List viewings") with the fields surfaced (property, applicant, time, status, feedback), which tells an agent exactly what a row contains. It does not explicitly distinguish itself from the sibling street_get_viewing, though the list-vs-single split is implied.

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?

Usage is only implied: "page with page and page_size" signals it is a paginated browse operation. There is no statement of when to prefer this over street_get_viewing or over filtered lookups, and no mention of the default exclusions (trashed, cancelled) that materially change results.

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