rta_search_bus_routes

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

No annotations are provided. The description reveals that credentials are required, which is a key behavioral trait. However, it lacks details on rate limits, pagination, error behavior, or data source limitations, leaving the agent with incomplete behavioral context.

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 short (two lines) and front-loads the purpose. However, conciseness comes at the cost of omitting parameter details and usage context. It is not overly verbose, but it sacrifices completeness.

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 has 3 parameters, no annotations, and an output schema (not described), the description provides minimal context. It does not explain how to use the parameters, what the output contains, or any constraints, making it incomplete for an agent to effectively invoke the 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 description coverage is 0%. The description does not explain any of the three parameters (limit, origin, route_number) beyond what is in the schema. For a search tool, the agent needs to know that origin and route_number are filters and limit controls result count, but this information is absent.

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 'Search Dubai bus routes via Dubai Pulse.' It specifies the resource (bus routes) and the verb (search). The mention of 'Tier 1' and sibling tools like 'rta_search_metro_stations' further distinguishes it from alternatives.

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 notes 'requires Dubai Pulse credentials,' indicating authorization is needed. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., when to search metro stations instead), nor does it mention any exclusions.

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