voice_ai_get_agents

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds no behavioral details beyond that, such as pagination behavior, default page size, or what happens with the query parameter. With no extra transparency, this is a minimal addition.

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 extremely terse ('List Agents') and functions more like a title than a description. It is concise, but it lacks structure and doesn't earn its place as a full description. It provides no additional context or elaboration, which makes it under-specified rather than efficiently concise.

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 that this is a list operation with a complex environment (openWorldHint), the description omits important details such as what the return payload looks like, whether pagination is supported beyond the page/pageSize params, and how 'query' and 'locationId' affect results. With no output schema and minimal description, an agent lacks sufficient context to correctly invoke and interpret the response.

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 coverage is 100% with descriptions for all four parameters (page, query, pageSize, locationId). The description itself ('List Agents') adds no parameter semantics beyond what the schema already provides. Since the schema carries the full burden, a 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 'List Agents' clearly states a specific verb (List) and resource (Agents). It distinguishes from the sibling voice_ai_get_agent (singular) which implies fetching a single agent, so the purpose is understandable. However, it doesn't explicitly mention that it lists all agents or support filtering, which could be more explicit.

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 no guidance on when to use this tool versus alternatives. There is no mention of when to choose this over voice_ai_get_agent or other listing tools like agent_studio_get_agents. The only implicit cue is the name itself, but no explicit context or exclusions are given.

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