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

Annotations already declare it read-only, idempotent and non-destructive, and the description adds real behavior beyond that: it always aggregates over the full calendar month of as_of_date regardless of the date passed, requires market rent to be configured, and reports unreachable Locations as skipped rather than failing. Those are exactly the operational traits an agent needs and none are in the annotations.

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 definition and report source before the mechanics, and every sentence carries information. The location paragraph is somewhat sprawling with parentheticals and an odd indented block, slightly hurting scannability but not wasting content.

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 an output schema present, the description needn't detail return values, yet it still enumerates the output columns and the per-Location labeling. The main remaining gap is the unexplained portfolio and property_ids parameters, which an agent would have to guess at given no schema descriptions.

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%, so description must compensate: it fully explains location (ID, comma list, "all", blank default, per-Location labeling) and clarifies as_of_date semantics (full calendar month, defaults to current month). But portfolio and property_ids get no explanation at all, leaving half the parameters undocumented in both schema and description.

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+metric with a one-line definition of loss to lease, then names the exact source (SummaryRentRoll, report 69) and the output shape (loss by unit type with market rent, in-place rent, loss, and loss-as-%-of-market). This clearly separates it from siblings like analyze_rent_roll or analyze_rent_composition, which report rent composition rather than the market gap.

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 concrete trigger phrasings ("what's our loss to lease", "how far below market are we") and a prerequisite (market rent must be set on units), plus the default time window. It does not explicitly name an alternative tool or state when not to use it, which keeps it short of a 5.

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