list_transcoders

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

No annotations are provided, so the description carries the full behavioral burden. It clearly signals a read-only listing operation and scopes it to configured transcoders, but it does not disclose pagination, response shape, or authorization requirements. This is adequate for a simple list operation but not richly transparent.

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 five words, front-loaded with the verb, and contains no filler or redundant information. Every word contributes to the meaning.

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?

With no parameters, no output schema, and no annotations, the description is the primary source of semantics. 'List all configured transcoders' is sufficient for a low-complexity enumeration operation, though it omits details about the response envelope or possible pagination. Overall it is complete enough for the tool's simplicity.

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 input schema already exhausts the parameter surface and there is nothing for the description to clarify. The phrase 'all configured transcoders' adds scoping context, which aligns with the baseline for a parameter-less tool.

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 a specific verb ('List') and a specific resource ('configured transcoders'), making the operation unambiguous. It also naturally distinguishes this tool from the sibling get_transcoder, which retrieves a single item rather than enumerating all.

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 tool is for enumerating all configured transcoders, but it provides no explicit when-to-use guidance, exclusions, or references to alternatives such as get_transcoder. The usage context is understandable but left largely to inference.

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