list_providers

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

With no annotations, the description carries the behavioral burden. It clearly indicates a read-only listing action and specifies the output content, and the phrase 'before issuing queries' signals that this tool does not perform searches. It does not discuss auth, rate limits, or empty-result behavior, but those are minor for this simple list operation.

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 sentences with the core action front-loaded and no filler. Every clause contributes either the action, the returned fields, or the recommended usage context.

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 tool with one optional parameter and no output schema, the description is complete: it names the resource, the returned fields, and the intended use phase. The only potential additions, such as pagination or error behavior, are low-value for this simple discovery call.

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 input schema already documents the optional 'tag' parameter with examples at 100% coverage, so the baseline is 3. The description mentions tags as a returned field but adds no new semantic detail about the parameter beyond the 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 uses the specific verb 'List' with the resource 'all available search providers' and enumerates the returned fields (names, descriptions, tags). It is immediately distinguishable from the sibling search_* tools, which execute queries, and from compare_engines/provider_health. The final clause reinforces the discovery 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?

It explicitly says to use it 'before issuing queries' to discover available search backends, giving a clear temporal/conditional context. It does not name alternatives or state when not to use it, but the guidance is sufficient for a simple discovery tool.

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