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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description adds useful behavioral detail by naming the pagination mechanism (next.offset or next.lastId) and disclosing the underlying GET /openhouses endpoint, though it does not discuss auth or vendor requirements.

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?

The definition is compact and front-loaded: the first clause establishes scope, the filter list follows immediately, and pagination plus endpoint are appended without filler. Every sentence contributes useful information.

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 17 parameters, no output schema, and full schema descriptions, the description gives enough context to call the tool: it identifies the resource, return association (open houses with listings), filters, and pagination. Minor gaps like sort behavior and vendor handling are adequately covered by the schema.

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%, so every parameter is already documented in the input schema. The description groups the filters into a readable list and mentions pagination, but adds no new parameter semantics beyond what the schema provides, making baseline 3 appropriate.

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?

The description states a specific verb and resource: list upcoming open houses together with their parent listings. This clearly distinguishes the collection operation from the sibling get_open_house tool, which retrieves a single open house.

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 description lists the available filters and explains pagination, which implies it is a search/listing tool. However, it never explicitly says when to use this instead of get_open_house or search_listings, so the usage guidance remains implied rather than stated.

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