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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds scope and output metrics but omits the optional email-report behavior tied to sendReportTo, which is only disclosed in the parameter schema, leaving a transparency gap.

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 description is compact with two functional sentences and a marketing tagline. The first sentence front-loads the core purpose, and the second lists outputs and use cases. The tagline is non-essential but not misleading, so it earns a strong score.

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 13 parameters and no output schema, the description adequately summarizes output metrics and use cases. However, it misses the optional email-report side effect and doesn't describe the return format beyond the metric list, leaving a minor completeness gap given the tool's complexity.

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?

The input schema has 100% description coverage for all 13 parameters, including extensive guidance on sendReportTo. The description adds no parameter-level detail beyond the schema, so it meets the baseline without enhancing parameter semantics.

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 states a specific verb ('Analyze') and resource ('cash flow for a rental property'), listing concrete outputs (NOI, cap rate, cash-on-cash return, DSCR) and property types (long-term rentals, Airbnb, buy-and-hold). This clearly distinguishes it from sibling calculators like calc-brrrr, calc-dscr, and calc-str_revenue.

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 description explicitly says it works for long-term rentals, Airbnb, and buy-and-hold analysis, giving clear context for when to use it. However, it does not name alternatives or provide when-not-to-use exclusions, though sibling tool names imply different analysis types.

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