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

Annotations already establish a safe, read-only, idempotent, closed-world operation, so the bar is lower. The description still adds real substance: each issue carries its fix, and an auto_fix field predicts what fix_gateway_issues would change, which tells the agent this call is a non-mutating preview. It does not discuss result volume, ordering, or whether issues are grouped, but the safety-relevant behavior is well covered.

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?

Three sentences, front-loaded with the payoff (what kinds of issues are reported) before the workflow instruction. The parenthetical examples earn their space by making 'setup problems' concrete. Slightly dense, but no sentence is filler.

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?

With no output schema, the description carries the burden of describing the return value, and it does: issues plus their fixes, plus an auto_fix field tied to the sibling tool. Combined with the read-only annotations and a fully documented single parameter, an agent has enough to call this correctly; only issue count/pagination and result ordering are unaddressed.

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?

There is a single parameter with 100% schema description coverage, and the schema already says the gateway_id comes 'From list_gateways'. The description adds no further meaning about that identifier or its accepted form, so the baseline of 3 applies — the schema does the work here.

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 makes clear this surfaces problems with a gateway — setup gaps (no base URL, missing credentials, no tools enabled), compiler warnings, and poor tool names/descriptions — and explicitly frames them as things to fix 'before or after publishing'. It separates itself from fix_gateway_issues by explaining that auto_fix previews what that sibling would do. The literal listing verb is only implied, so it falls just short of a perfect verb+resource statement.

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?

It gives concrete timing guidance ('before or after publishing') and an explicit workflow instruction to show issues and proposed fixes to the person before changing anything, which effectively routes the agent to review with this tool before calling fix_gateway_issues. It stops short of stating explicit exclusions, e.g. that it does not report runtime/log problems (that would be list_gateway_logs).

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