retell_list_llms

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

No annotations are provided, so the description carries the transparency burden. It states the tool lists configurations, which clearly indicates a read-only operation, but it does not disclose potential details like pagination, ordering, or whether the list includes full configuration data or summaries. Given the simplicity of a list operation, this is minimal but not misleading.

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 a single concise sentence with no filler or redundant information. It front-loads the action and resource, earning a perfect score for efficiency.

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 simple tool with no parameters and no output schema, the description adequately states what it does and the scope. However, since there is no output schema, it would be helpful to mention what information is returned (e.g., configuration names and IDs, or full details). Still, the description is sufficient for an agent to select and invoke the tool correctly.

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. No parameter explanations are needed, and the baseline for zero-parameter tools is 4. The description adds no parameter information, but that is unnecessary here.

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 is specific: 'List all Retell LLM configurations in your account.' It clearly states the verb (List), the resource (Retell LLM configurations), and scope (in your account), which distinguishes it from related tools like retell_get_llm (single LLM) or retell_create_llm.

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 usage when you need an overview of all LLM configurations, but it does not explicitly mention alternatives or when not to use it. For example, it does not point to retell_get_llm for retrieving a single configuration or to create/update for modifications. The context is clear but lacks exclusions.

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