discover_gateway_tools

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

The description reveals the return type but adds no information about side effects, permissions, performance implications, or behavior beyond the schema. With no annotations provided, the description carries the full burden and fails to disclose whether this tool queries live servers, caches results, or requires prior setup.

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 short sentences put the purpose first and the return value second. There is no filler or redundant information, making it highly concise and well-structured.

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?

While the description explains the output and has no parameters, it does not clarify the relationship to sibling tools like list_enabled_tools or list_available_servers. Given the rich sibling context, a more complete description would mention when this tool should be used or how it differs from nearby alternatives.

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, so the schema is empty. Per the rubric, the baseline for 0 params is 4. The description adds context about the tool's scope ('from enabled Docker MCP servers'), which is sufficient and meaningful.

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 tool's function with a specific verb ('Discover') and a specific resource ('tools available from enabled Docker MCP servers'). It also specifies the return value. However, it does not explicitly differentiate from sibling tool 'list_enabled_tools', which may overlap in purpose.

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. It does not mention any exclusions, prerequisites, or relationships to sibling tools like list_enabled_tools or list_available_servers, leaving the agent uncertain about the best tool for a given context.

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