calculate_loan_to_value

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

No annotations exist, so the description should fully disclose behavior. It states outputs but omits side effects, permissions, rate limits, or error behavior. 'Compute' implies read-only, but not explicitly stated.

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, front-loaded with purpose, efficient. Every sentence adds value: purpose, usage, inputs, outputs, sibling reference. No fluff.

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 simple calculator with full schema and output schema present, the description covers purpose, inputs, and outputs. Missing error handling or edge cases, but adequate for basic use.

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 covers 100% of parameters with descriptions (property_value, loan_amount). The description repeats these without adding new meaning (e.g., units, constraints). Baseline 3 is appropriate.

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 it computes Loan-to-Value ratio for mortgage risk, specifying the context (mortgage application/PMI). It mentions 'related immobilier calculators' via list_bundles, but doesn't explicitly differentiate from all similar calculate siblings.

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?

Provides clear usage context ('mortgage application or PMI thresholds') and lists inputs, but lacks explicit when-not-to-use or alternative tools. The sibling reference is minimal guidance.

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