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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds genuine context beyond that: 'customer-safe' signals output redaction, and 'email-verified application session' discloses an auth/eligibility prerequisite on the token. No error or expiry behavior is described.

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?

A single front-loaded sentence with no filler; the resource and its scoping constraint come first and nothing is repeated from the schema or 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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. What the agent still needs — behavior on invalid/expired session tokens — is absent, but for a one-parameter read tool the definition is close to complete.

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 0% and the single parameter is undocumented in the schema, so the description must carry the load. It does partially: it establishes that sessionToken must be tied to an email-verified application session, implying the token is a session credential rather than an arbitrary id. No format, source, or freshness detail is given.

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 (Read) and resource (customer-safe viewing proposals and confirmed viewing state) with an explicit scope (one email-verified application session). This clearly separates it from the mutating viewings siblings (propose_availability, respond_to_proposal), though it never names them. Clear, but no explicit sibling differentiation in text.

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?

There is no when-to-use/when-not guidance and no alternative tool named. The scope phrase 'for one email-verified application session' implies the calling context but does not tell the agent when to reach for this versus viewings.respond_to_proposal or a booking status tool.

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