list_tools

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

The description correctly indicates the tool lists tools with descriptions, which is a read-only operation. However, with no annotations provided, the description carries full transparency burden and does not mention any potential requirements (e.g., authentication) or other behavioral traits, though the simplicity of the tool makes this acceptable.

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 sentence that is concise and front-loaded, containing no unnecessary words. Every word serves a purpose, making it efficient for an agent to parse.

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 no parameters and an output schema exists (to describe return values), the description is complete. It succinctly tells what the tool does without needing additional context.

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 no parameters and schema coverage is 100% (trivially). Per guidelines, 0 parameters baseline is 4. The description does not need to add parameter information as none exist, so this score is appropriate.

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 clearly states the function: listing all available tools and their descriptions. It uses a specific verb ('list') and resource ('all available tools'), which distinguishes it from sibling tools that perform actions like adding rules, clearing traffic, or searching.

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 guidance on when to use this tool versus alternatives. Given the large set of sibling tools, explicit usage context (e.g., 'Use this to discover available tools before calling others') would be helpful but is absent.

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