List engine providers and their catalogs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description contributes nothing beyond that – no note on whether results are paginated, scoped to the current account/namespace, or cached. With the lower bar set by annotations, this flat restatement earns only a 2.

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?

Single short sentence with zero waste and the key concept front-loaded. It is efficient to the point of under-specification, but there is no padding or throat-clearing to penalise.

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?

No output schema exists, and this tool aggregates providers alongside their catalogs, so the description is the only place an agent could learn what 'providers' and 'catalogs' mean (engine types? backend offerings?) in this specific product. It never does, leaving the return content opaque beyond the verb.

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 takes zero parameters, which normally sets a baseline of 4; however the description also does nothing to characterise the response shape, and 'catalogs' is left as an unexplained term. A 3 reflects that there is simply no parameter surface to discuss, while noting nothing compensates for the ambiguity of the domain terms.

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?

Tautological: description restates name/title.

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?

There is no when-to-use guidance at all: no mention of when to pick this over provider_get for a single provider, or how it relates to backends_list. Usage must be inferred entirely from the bare name.

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