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

Annotations declare readOnlyHint=false and idempotentHint=false, and the description explains why: "Returned alerts are marked retrieved," i.e. the call mutates alert state so a repeat call differs. It also discloses the payload shape (property, source, previous/current values, detection time, freshness, match reason) and adds a meaningful guardrail against overstating the wording. It does not mention permissions or rate limits.

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?

Front-loaded with the resource and its alert vocabulary, then filtering, then payload, then the wording guardrail. Efficient overall, though the inline enumeration of ten alert types is a long block that partly duplicates the schema enum.

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 no output schema, the description usefully compensates by describing the alert fields, the freshness/match-reason metadata, and the side effect of marking alerts retrieved. The remaining gap is pagination/limit behavior and the omitted alert types, which are minor for a 4-parameter read-with-side-effect tool.

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 only 25%, so the description has to carry more weight. It covers the `types` and `watchlist` filters in prose and its "marked retrieved" note implicitly explains `include_already_retrieved`, but `limit` is never addressed and the enumerated alert list omits four schema enum values (NEW_LISTING_OBSERVED, PRICE_INCREASE, PROPERTY_PENDING, PROPERTY_SOLD).

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?

Names a specific verb+resource (retrieve monitoring alerts) and enumerates the alert categories it returns, which frames it distinctly from search_properties and get_property_history. However, it never explicitly names a sibling or states what makes it different, so sibling differentiation is implied rather than stated.

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?

"Filter by types (e.g. price changes only) or watchlist" gives a usable filtering hint, which is more than nothing. But there is no when-to-use/when-not guidance and no routing to alternatives such as get_property_history for older events or search_properties for non-alert discovery.

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