retell_get_llm

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

No annotations are provided, so the description carries the burden for behavioral disclosure. 'Get' implies a read-only operation, but the description does not explicitly state safety, error behaviors, or what exactly is returned. It adds minimal context beyond the tool name.

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, focused sentence that immediately states the tool's purpose. It uses no unnecessary words and is well-structured for quick parsing.

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?

Given the simplicity of the tool (one parameter, no output schema), the description is adequate. It communicates that the result is 'details' of the configuration, though it could be more explicit about the return format or that it is a read-only operation. Overall, it is complete enough for a simple retrieval 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?

Schema description coverage is 100% with llm_id well-defined as 'The unique ID of the LLM to retrieve.' The description does not add additional meaning to the parameter, but the schema already provides sufficient clarity, so baseline 3 is appropriate.

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 clearly states the tool retrieves details of a specific Retell LLM configuration, using the verb 'Get' and specifying the resource. This distinguishes it from sibling tools like retell_list_llms (which lists all) and retell_create_llm/update/delete (which mutate).

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 have a specific LLM ID, but provides no explicit guidance on when to choose this over alternatives like retell_list_llms. It does not state exclusions or mention that this is for a single item vs. listing.

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