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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral detail beyond that: filters combine with AND (only 'in' gives OR, per schema), results are paged, and next_offset indicates continuation. No auth, rate-limit, or result-shape caveats, but for a read-only search this is solid.

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?

Three short sentences, front-loaded with what the tool does and the key AND/paging semantics. The trailing POST path is minor low-value detail but takes only a clause.

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?

No output schema exists, and the description partially compensates by naming next_offset as the pagination cursor in the reply. With 0 required params, 5 fully documented parameters, and a mutation-free profile, an agent has enough to call this correctly; the actual row shape remains undisclosed.

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%, including the AND-combination semantics, paging defaults, and order_by guidance, so the schema carries the load. The description restates the AND rule and paging hint but adds no new meaning (e.g., criteria/limit interaction or recommended filter patterns).

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 and glosses the resource domain ('listing events (open homes and inspections)'), which is genuinely clarifying. It does not distinguish itself from the nearest sibling, rex_search_appointments, which could plausibly cover inspections, so it stops short of 5.

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?

Gives a concrete prerequisite workflow: call rex_describe_search_fields with service ListingEvents before building criteria, and use next_offset to continue paging. It does not say when to prefer this over rex_search_appointments or other search siblings, so no exclusions are covered.

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