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

readOnlyHint=true already declares this a safe read, so the safety profile is covered by annotations. The description adds which fields come back, which is useful, but says nothing about pagination, result limits, ordering, or rate limits for what is presumably a large collection endpoint.

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 covering resource and returned fields, plus the underlying API endpoint. Efficient, though the endpoint string is marginally useful to an agent and slightly pads the definition.

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?

A simple read-only list tool with one optional parameter and no output schema; the description compensates for the missing output schema by naming the fields returned. Missing only collection-level behavior (pagination/limits), which is a minor gap.

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% and the single agency_uid parameter is fully documented in the schema (default env var plus pointer to hostfully_list_agencies). The description adds no parameter-level detail, so the baseline 3 applies.

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 (List) and resource (agency's guest records) and enumerates the returned fields (names, email, phone, address, profile notes). This clearly distinguishes it from sibling list tools such as hostfully_list_owners, hostfully_list_properties, and hostfully_list_agencies.

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?

The listing intent is implied by the verb and resource, but there is no explicit guidance on when to use this vs other list/search tools, nor any note about prerequisites beyond the schema's default-UID hint. Adequate but with a clear gap.

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