list_avatars

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 adds useful context about the large number of avatars and the need to narrow results, but it doesn't detail return format, pagination, or sorting. This is adequate but not exceptionally rich.

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?

Two sentences, front-loaded with the primary action and then the key usage tip. No wasted words; every sentence contributes useful information.

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 list tool with three well-documented params and no output schema, the description covers purpose, usage, and a critical performance characteristic. It could mention the response structure more explicitly, but it already notes 'with their avatar_id and preview video,' making it fairly complete.

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% and every parameter (limit, search, include_talking_photos) has a clear description. The description adds minimal extra meaning beyond mentioning 'search term,' so the baseline of 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's function: listing avatars with their avatar_id and preview video. It uses a specific verb and resource, and naturally distinguishes itself from sibling tools like list_voices and list_videos by explicitly focusing on avatars.

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 provides clear usage context: 'before picking one for create_video' and strongly advises always passing a search term due to the account scale. It doesn't explicitly mention alternatives or when not to use, but the guidance is actionable and relevant.

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