list_ai_gateways

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

No annotations exist, so the description carries the full burden of disclosing behavior. It only states the listing operation and account scope, without mentioning pagination, response shape, ordering, rate limits, or other runtime behavior an agent may need to know.

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, front-loaded sentence with no filler. It states verb, resource, and scope in ten words, which is appropriately concise for a one-parameter list operation.

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?

The operation is simple and the parameter is fully documented, so an agent can likely invoke it with account_id. However, there is no output schema and the description does not mention pagination or result structure, leaving an important gap for an agent that needs to consume the returned data.

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% and the single account_id parameter is already described as 'The account ID'. The description's phrase 'in an account' echoes that schema meaning without adding new parameter details, so it neither improves nor harms parameter clarity beyond the baseline.

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 uses a specific verb ('List') and a specific resource ('AI Gateway instances') with account scope, making the operation immediately clear. It also distinguishes itself from sibling tools such as list_ai_gateway_routes, list_ai_gateway_datasets, and get_ai_gateway_logs by targeting gateway instances specifically.

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?

No guidance is provided on when to use this tool versus alternatives like list_ai_gateway_routes or get_ai_gateway_logs. The description gives no exclusions, preconditions, or comparisons to sibling tools, leaving the agent to infer usage solely from the name.

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