ghl_voice_ai_list_agents

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

Annotations already provide readOnlyHint, idempotentHint, etc. Description adds value by disclosing OAuth scopes (voice-ai-agents.readonly), pagination behavior, and endpoint details. This goes beyond the annotations, providing clear behavioral context.

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?

Description is concise at four lines, front-loading the purpose. Includes necessary technical details (endpoint, version, scopes) without excessive verbosity. Each sentence adds value, though the endpoint block could be seen as slightly dense.

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?

No output schema is provided, so description should compensate by explaining return format. It states 'retrieve a paginated list of agents' but does not detail the structure of the list (e.g., array of agent objects with fields). This leaves some ambiguity for the agent.

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%, so baseline is 3. The description mentions pagination params for paging through result sets, but does not add significant new meaning beyond what is already in the schema descriptions (e.g., page, pageSize, locationId). Adequate but not enhanced.

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?

Description clearly states 'List Agents' and 'Retrieve a paginated list of agents for given location.' This provides a specific verb (retrieve/list) and resource (agents), and distinguishes from other agent tools like create, delete, or patch agents.

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?

Description mentions required locationId and pagination parameters, but does not explicitly contrast with alternatives like ghl_voice_ai_get_agent (single agent retrieval) or state when not to use this tool. Implied usage is for listing all agents, but lacks explicit guidance.

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