rental_dispute_guide

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

Without annotations, the description discloses key behaviors: returns guide and optionally computes fee with formula (3.5% of annual rent, AED 500 floor, AED 20,000 cap). It does not mention potential side effects, but as a read-only operation, this is transparent enough.

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 sentences, no redundant information, front-loaded with main purpose. Every sentence adds value without fluff.

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 tool's complexity (one optional param, output schema exists), the description covers the main return value (guide) and conditional fee. It doesn't detail the format of the guide, but the output schema likely handles that. Sufficient for a straightforward guide tool.

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 coverage is 100% for the single parameter, and description adds conditional behavior ('If annual_rent is provided, also compute...') and the fee formula, enriching meaning beyond the schema description. However, the schema already states 'Optional... to compute the filing fee', so the added value is moderate.

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 it 'Returns the Rental Disputes Centre (RDC) filing guide' and optionally computes the filing fee. This specifically identifies the resource and action, distinguishing it from other guide tools among siblings like 'ejari_guide' or 'submission_guide'.

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 for rental dispute filing guide retrieval and fee computation, but provides no explicit when-to-use or when-not-to-use guidance relative to alternatives. It does not mention exclusions or context for preferring this tool over similar ones.

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