ghl_agent_studio_get_agents

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

With no annotations, the description carries full behavioral burden. It only says 'List all' but does not disclose pagination behavior despite limit/offset parameters, nor does it describe the response format or any side effects. The word 'all' is potentially misleading given the presence of limit and offset parameters.

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 concise sentence with no fluff, front-loading the core purpose. However, it is slightly too terse, omitting useful details that could be included without sacrificing conciseness.

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?

The tool appears simple but lacks an output schema, and the description does not clarify return values, pagination, or how this listing tool relates to the singular get_agent variant. The pagination discrepancy with 'all' and missing parameter explanations leave the description incomplete for practical use.

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 only 33% (locationId), and the description does not compensate by explaining limit/offset or their defaults. It adds no meaning beyond the schema, leaving two of three parameters effectively undocumented.

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 a specific action ('List') and resource ('AI agents in Agent Studio'), distinguishing it from sibling tools like ghl_agent_studio_get_agent (singular) and create/execute variants. The scope is 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 implies usage when a list of all agents is needed, but provides no explicit guidance on when to use this versus alternatives (e.g., get_agent for a specific agent) or any exclusions. No alternatives or prerequisites are mentioned.

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