calculate_rent_increase_irl

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

With no annotations, the description carries full burden. It states it calculates and returns a specific object, implying it is a read-only calculation with no side effects. However, it does not explicitly disclose behavioral traits beyond the obvious (e.g., no mention of rate limits, data usage, or confirmation that it's safe to call repeatedly).

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 two sentences, front-loaded with the core purpose, and includes the return format. Every sentence adds value; no redundant or extraneous information. Highly concise.

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 3-parameter calculation tool, the description covers the purpose and return format. It references list_bundles for related calculators. However, it does not explain what 'IRL' stands for or where to obtain the index values, which could be helpful for unfamiliar agents. Still, given the simplicity and presence of an output schema (implied by return description), it is mostly complete.

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% description coverage for all three parameters (current_rent, old_irl, new_irl) with clear meaning. The description adds no additional parameter semantics beyond what the schema already provides. 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 'Calculate rent increase allowed by French IRL index', specifying the verb (calculate) and resource (rent increase using French IRL index). It distinguishes from siblings by referencing a specific French index, making its purpose unique among many calculate 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?

The description provides a hint to 'See list_bundles for related finance-france calculators', suggesting related tools but not explicitly stating when to use this tool vs alternatives. No clear exclusion or comparison to specific siblings like calculate_rent_ratio or calculate_rental_profitability.

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