rera_rent_increase

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

No annotations are provided, so the description must carry the full burden. It explains the calculation logic and what is returned (gap %, max increase %, max new rent), but does not disclose whether it requires authentication, makes external API calls, or handles errors. For a computation tool, this is adequate but not 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?

The description is concise with two sentences. The first sentence states the purpose, the second explains the mapping and outputs. No redundant information.

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 the input schema is fully described, an output schema exists (not shown but indicated), and the description covers the mapping logic, it is mostly complete for a computation tool. However, it lacks error handling or edge case information, which is minor for a deterministic calculator.

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 100% with descriptions for both parameters. The description adds value by explaining the mapping logic between current rent and area average rent, and what the outputs represent, going beyond the schema.

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 computes the maximum legal rent increase under Dubai Decree 43 of 2013, specifying the verb 'compute' and the resource 'rent increase'. It distinguishes itself from siblings like rent_estimate and rental_dispute_guide by focusing on a specific legal formula.

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 when to use (when needing to compute max rent increase under Dubai decree) by explaining the mapping logic. It does not explicitly state when not to use or list alternatives, but the specificity makes it clear.

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