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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds useful behavioral context by explaining that the senior loan is solved as the remainder and listing the outputs, but it does not discuss assumptions around fixed senior amounts, DSCR targets, or standby-interest handling beyond what the schema covers.

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 front-loaded with the core operation and remainder-solving behavior, then efficiently lists inputs and outputs before closing with the usage condition. It is dense but every sentence contributes information, and there is no filler.

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?

For a 21-parameter modeling tool, the description is appropriately complete when read alongside the fully documented schema, annotations, and output schema. It covers the purpose, general inputs, outputs, and use case, though it could mention the fixed seniorAmount alternative and targetDSCR comparison more explicitly.

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%, so the parameter meanings are already fully documented. The description groups the key inputs—price, working capital, closing costs, equity sources, seller-note terms, senior-loan terms, and cash flow—but adds little semantic detail beyond the schema defaults, ranges, and enum documentation.

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 action and object: laying out sources and uses for a business acquisition and solving the senior loan as the remainder. It goes beyond the title by specifying outputs such as the funding gap, source shares, debt service, coverage, and sensitivity, which distinguishes it from a generic acquisition-loan model.

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 an explicit use condition: 'Use when the user asks how the whole purchase gets funded.' That is clear context, but it does not state when to avoid this tool or name sibling alternatives such as model_acquisition_loan or model_seller_note.

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