rta_search_metro_stations

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

With no annotations, the description carries full burden. It discloses that only operating lines are covered and explicitly excludes Blue and Gold Lines. It mentions authentication requirements. While it does not discuss rate limits or pagination, these are less critical for a search tool.

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 three succinct sentences, front-loaded with the main purpose. Every sentence adds value: main function, credentials, exclusions. No wasted words.

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 medium complexity, the description covers purpose, scope, exclusions, and authentication. With a full input schema and output schema present, the description is complete and leaves no critical gaps.

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%, so the schema fully describes the line and limit parameters. The description adds context about which lines are operating (Red, Green, Route 2020) but does not provide additional parameter-level meaning beyond what is in 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 states 'Search Dubai Metro stations' with a specific resource (Dubai Metro stations) and verb (Search). It distinguishes from sibling tools like rta_search_bus_routes by focusing on metro stations and specifying the data source (Dubai Pulse).

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 explicitly states prerequisites (Tier 1, Dubai Pulse credentials) and when not to use (for Blue and Gold Line stations under construction). However, it does not name alternative tools for those excluded lines, leaving some guidance implicit.

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