retell_get_agent

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

With no annotations provided, the description carries the burden of behavioral disclosure. It conveys a read-only operation via 'Get' and adds 'detailed information' as context, but it does not mention error scenarios (e.g., missing agent), permission requirements, or the exact structure of the returned data. This is adequate but not fully 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 a single, front-loaded sentence that captures the essential purpose and parameter without any wasted words. It is appropriately concise and well-structured for a simple retrieval tool.

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 tool with one parameter and no output schema, the description is minimal but serviceable. It fails to specify what fields 'detailed information' includes or how it differs from other get-type tools like retell_get_agent_versions. Given the simplicity, a 3 reflects a complete-but-basic offering.

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 input schema already documents agent_id with 100% coverage, and the description only repeats that retrieval is 'by its ID'. No additional semantic detail about the parameter or its expected format is provided, so the description adds nothing beyond the schema.

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 action ('Get'), the resource ('detailed information about a specific Retell AI agent'), and the scope ('by its ID'). This effectively distinguishes it from siblings like retell_list_agents (which lists many agents) and retell_get_agent_versions (which retrieves version history).

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 intended usage is implied: use this tool when you have an agent_id and need detailed information. However, it does not explicitly state when to use it over alternatives (e.g., 'use list_agents to find IDs') or exclude related tools like retell_get_agent_versions, leaving the guidance implicit.

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