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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful context about the breadth of products covered (flipping, Airbnb, BRRRR, multifamily), which goes beyond the annotations. No contradictions.

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?

Three sentences, with the first front-loading the primary purpose and the second listing coverage. The final marketing sentence ('USDV Capital — Your Real Estate CFO...') is promotional filler that doesn't help an agent select or invoke the tool, keeping it from a 5.

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?

The tool is simple (one optional param, no output schema), and annotations cover safety. The description adequately explains what products are covered and hints at the return ('detailed information'). It doesn't detail output format, but given low complexity and strong annotations, it is sufficiently complete.

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 100% (the single parameter product_type has a clear description). The tool description does not elaborate on parameter usage, but the schema already documents it. Baseline 3 applies because the description adds no additional parameter meaning.

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 clearly states 'Get detailed information about capital solutions' with a specific resource (capital solutions) and enumerates concrete product types (Fix & Flip, DSCR, bridge, construction). This distinguishes it from siblings like eligibility-check and calc-* calculators, which focus on eligibility and calculations.

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?

No explicit when-to-use or alternative guidance is provided. The description implies usage through its product list, but it doesn't explicitly say when to choose this over eligibility-check or other related tools. Context is present but not directly stated.

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