calculate_debt_capacity

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

As a stateless calculation tool, the description adequately implies behavior: it computes based on inputs and returns specified fields. No annotations are provided, so the description carries the burden, and it does so sufficiently.

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?

Two concise sentences: first states purpose and output, second directs to related tools. No wasted words, front-loaded, and easy to parse.

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 well-documented schema, the description is complete: it explains the rule, output shape, and points to related tools. The lack of output schema is compensated by mentioning the return object.

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?

The input schema has 100% coverage with descriptions for all 4 parameters. The description adds no additional parameter context beyond what is already in the schema, so a baseline of 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 the tool calculates maximum loan capacity using the French HCSF 35% debt ratio rule, and lists the return fields. It does not explicitly distinguish from sibling tools but the specific rule and domain make it distinct.

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?

The description implies usage context by mentioning the debt ratio rule and directing to 'list_bundles' for related calculators, but does not provide explicit when-to-use 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.