list_ai_gateway_routes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that routes are listed, with no mention of pagination, read-only semantics, response shape, error conditions, or account-level vs gateway-level behavior.

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 a single focused sentence with no filler words, and it front-loads the core operation and resource. It is concise, though it could have added a bit more context without becoming bloated.

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?

For a two-parameter list operation with no output schema or annotations, the description is minimally sufficient: an agent can infer the intent and required parameters. However, it lacks details such as return format, pagination, or how the route list is scoped to the gateway, so it is not fully complete.

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 already documents both parameters. The description does not add meaning beyond the schema; it does not explain how account_id and gateway_id relate or how to discover valid gateway IDs, but the baseline of 3 is appropriate given full schema coverage.

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 a specific verb ('List'), a specific resource ('routes'), and the domain ('AI Gateway'). It clearly distinguishes from sibling tools such as list_ai_gateways (lists gateways, not routes) and get_ai_gateway_route (retrieves a single route).

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?

There is no guidance on when to use this tool versus alternatives like get_ai_gateway_route or list_ai_gateways. The description implies the basic use case but provides no preconditions, exclusions, or selection criteria.

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