Lends Math Convert Decimals Exact

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

Annotations already provide read-only, idempotent, and non-destructive signals. The description adds operation-specific behavior: returning null when downscaling is inexact, which is non-obvious and important. It does not detail exact return value format or edge cases, but substantial behavioral context is provided.

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 a single, front-loaded sentence with no filler. It conveys the action, the resource, and the key behavioral condition without redundancy.

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 read-only math utility with strong annotations, the description covers the core units and result behavior. The absence of an output schema is partially mitigated by stating the null condition, though the exact success return type and usage guidance remain implied rather than explicit.

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 0%, so the description must help interpret parameters. 'Raw units between decimal scales' contextualizes amount as raw units and from/toDecimals as scales, but it does not document each parameter individually. Self-explanatory parameter names and schema constraints compensate for much of this gap.

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?

States a specific operation: converting raw units between decimal scales, with an exactness condition. The phrase 'returning null if downscaling is inexact' clearly distinguishes it from non-exact or approximate conversion tools.

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?

Usage is implied rather than explicit: an agent can infer to use this when exact decimal-scale conversion is needed. However, no alternatives are named and no when-not-to-use guidance is given, leaving comparison with sibling tools like lends_math_scale_price_to_e8 to inference.

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