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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's added value is the trailing ~90-day default window and the default 50% drop threshold, plus the shape of what gets returned. It does not discuss cost, rate limits, or data freshness, but it adds meaningful operational context beyond 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?

The output summary is front-loaded before the sample questions, and the parenthetical report identifier is compact. The phrasing is a bit fragmentary ('Month-over-month payment trends (PaymentComparison, 32)') but every line conveys usable 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 an output schema present, the description need not explain return values, yet it still outlines the three result surfaces, which helps an agent predict fit. The remaining gap is the unexplained filter parameters, but for a read-only analytics tool the coverage is close to sufficient.

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 0% across 6 parameters, so the description carries the burden. It clarifies drop_threshold_pct (payment drops larger than this value, default 50%) and the default date window, but says nothing about top_n, portfolio, property_ids, start_date, or end_date semantics or formats. Partial compensation only.

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 names a specific verb and resource (month-over-month payment trends / collections) and enumerates the three outputs it produces: monthly totals with % change, per-property rollup, and tenant-level drops. That lets an agent separate it from siblings like analyze_delinquency or analyze_rent_roll without opening a schema.

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?

It gives concrete selection cues via the 'Answers:' list ('which tenants stopped paying', 'how did collections trend last quarter'), which implicitly tells the agent the conditions this tool fits. It stops short of naming an alternative tool or stating when not to use this one, so it falls just below the top mark.

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