calculate_debt_to_income

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

With no annotations, description carries transparency burden. It states inputs and outputs but does not disclose potential side effects, data handling, or authentication requirements. Adequate for a read-only calculation, but could be more thorough.

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 well-structured sentences with front-loaded information. No redundant phrases, efficient and clear.

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?

Given low complexity and presence of output schema, description covers purpose, use cases, inputs, outputs, and related resources. Minor gap: no mention of limitations or permissions, but overall sufficient.

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 already covers both parameters with descriptions (100% coverage). Description only reiterates inputs, adding minimal value. 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?

Description clearly states verb 'Compute' and resource 'debt-to-income (DTI) ratio', with specific use cases. However, it does not explicitly differentiate from sibling tools like calculate_debt_capacity or calculate_debt_service_ratio.

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 context: 'Use for mortgage qualification or financial health checks' and references list_bundles for related calculators. Lacks explicit exclusions or when-not-to-use guidance.

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