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

Annotations already declare readOnlyHint and idempotentHint, lowering the bar. The description adds useful context about included cost components and capital strategy assessment, but it also includes a promotional sentence about USDV Capital financing that doesn't describe tool behavior and omits mention of the sendReportTo (email report) feature. This is a moderate addition beyond annotations, not a full disclosure.

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 first two sentences are efficient and front-loaded, but the final sentence about USDV Capital's financing terms is irrelevant to tool usage and does not earn its place. This extraneous marketing content prevents a higher conciseness 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 no output schema, the description should clarify what the tool returns (e.g., ROI figure, breakdown, report). It lists cost categories but does not state the output format, and it fails to mention the sendReportTo capability entirely. While the schema covers the email parameter, the description leaves ambiguity about the tool's overall behavior for an agent.

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 provides 100% parameter descriptions, so the baseline is 3. The tool description does not add any parameter-specific details beyond what the schema already covers; it just references cost categories that map to existing properties without elaborating formats or constraints.

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 opens with a specific verb and resource: 'Calculate projected ROI for a fix-and-flip or house flip project.' It enumerates cost categories and profit analysis, and explicitly notes BRRRR acquisition phase applicability, which distinguishes it from sibling calculators like calc-brrrr or calc-rental_cashflow.

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 gives clear context: it is for flip projects and also useful for BRRRR acquisition phase analysis. However, it does not explicitly name alternative tools or state when not to use it, so it misses the full 'when/alternatives' guidance that would merit a 5.

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