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

With no annotations provided, the description carries the full disclosure burden. It explicitly states 'Read-only; no payment or provider execution,' which is a critical safety trait that prevents misuse. However, it does not describe the response format, pagination, or other potential side effects, though these may be less critical for a zero-parameter list 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?

Two concise sentences with no filler. The primary purpose is stated first, followed by a key safety note. The description is front-loaded and every word serves a purpose.

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 simple list tool with no parameters and no output schema, the description adequately covers purpose, safety, and lack of execution. It does not mention pagination or return structure, but these are unlikely to prevent correct invocation. The read-only disclosure compensates for the absence of annotations.

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?

The tool has zero parameters, and the input schema is already fully covered (100%). Per the baseline rule for zero parameters, a score of 4 is appropriate since there are no parameter semantics for the description to add beyond the empty 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 a specific verb ('List') and resource ('Gate Network toll gates'), clearly distinguishing it from siblings like describe_gate or search_gates by indicating it returns all available gates. The read-only qualifier further differentiates it from tools that execute payments or provider calls.

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 provides no explicit guidance on when to use this tool over alternatives. It implies a broad listing via 'available' but does not mention search_gates for filtered queries or describe_gate for a single gate, leaving the agent to infer selection criteria from sibling names.

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