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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description still adds real behavioral content beyond that: the underlying data source (AgedReceivables report 78) and the transformation performed (aggregation per property, ranking of delinquent tenants). It does not mention constraints such as permissions or row limits, keeping it at 4.

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 aging buckets, then one sentence on processing, then example questions. Compact and every line is relevant, though the fragmented multi-line formatting is slightly choppier than a single tight paragraph would be.

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?

An output schema exists, so return values need not be described, and annotations fully cover the safety profile. What remains is mostly adequate for a read-only analytical tool with all-optional parameters, though the unexplained as_of_date and property_ids scoping leaves a modest gap.

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%, so the description must carry all four parameters. It only illuminates 'portfolio' (via 'for a portfolio' and the GSP example) and weakly implies 'top_n' through ranking. The critical 'as_of_date' for an aging analysis and the 'property_ids' scoping parameter are entirely unexplained in both description and schema.

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 resource (aged receivables), the exact aging buckets (30 / 31-60 / 61-90 / 91+), the scope (a portfolio), and the processing (aggregates per property, ranks delinquent tenants). An agent can immediately distinguish this from the payables counterpart, analyze_aged_payables, and from general AR tools like analyze_rent_roll.

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 three example questions ('who's most past-due', 'how much is 90+ days old', 'what's our total AR for the GSP portfolio') give concrete invocation contexts that map directly onto the tool's output. It stops short of naming alternatives or stating when not to use it (e.g., versus analyze_delinquency), so it falls 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.