list_providers

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

No annotations are provided, so the description carries the full burden. 'List' implies a read-only operation, and the description adds useful context about scope ('configured', 'BYOK') and returned content. However, it does not disclose potential behaviors such as whether it only returns built-in providers, if it can be empty, or whether any configuration is required first.

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?

A single, front-loaded sentence that conveys the action, the subject, and the output contents without filler. Every word adds value.

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 zero-parameter listing tool with no output schema, the description adequately conveys the purpose and the returned categories. It does not explain the BYOK acronym or give examples of capabilities, but those are minor omissions for such a simple tool.

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?

There are zero parameters, so the description does not need to explain parameter behavior. The baseline for no-parameter tools is 4, and nothing in the schema requires additional clarification.

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?

States a specific action 'List' with a clear resource 'configured BYOK generation providers' and explicitly names what is returned: 'their models and capabilities'. It is easily distinguished from sibling render_image and render_video, which perform generation rather than listing providers.

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 implies this is a discovery/list operation used to inspect available generation providers, especially before rendering tasks. However, it does not explicitly state when to use this tool versus alternatives or exclude cases, though the sibling names make the distinction reasonably clear.

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