rta_salik_tariff

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

The description discloses a future behavioral change (VAT from 2026-06-01) and that the response includes VAT-inclusive amounts. However, it does not explicitly state the tool is read-only or mention error/rate-limit behavior, though the nature of 'return reference data' implies safety.

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 four sentences each serving a distinct purpose: purpose, authentication, future change, scope limitation. No 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 no parameters and an output schema present, the description fully covers the tool's purpose, auth requirements, future behavior, and limitations. Complete for an AI agent.

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 zero parameters, so schema coverage is 100%. The description adds no parameter details, but none are needed. Baseline score of 4 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 'Return Salik toll tariff reference data', which is a specific verb+resource. The tool name 'rta_salik_tariff' distinguishes it from siblings like 'salik_toll_estimate' that estimate costs for trips.

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 specifies 'Tier 1, requires Dubai Pulse credentials' for authentication context. It also clarifies what the tool does not cover ('Account balances, trips, and violations are NOT exposed'), preventing misuse.

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