ghl_conversation_ai_get_agent

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

No annotations are present, so the description must carry the behavioral disclosure burden. It only states the action without describing return format, error handling, auth requirements, or side effects. For a read operation, this is minimal and leaves significant behavioral details undisclosed.

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?

Single sentence, zero wasted words. It front-loads the purpose efficiently and contains no filler or repetition.

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 is simple with one parameter and no output schema, so the description is mostly adequate for a basic get-by-ID. However, it could mention the return value or the relationship to search_agents, especially given multiple get_agent siblings. The absence of behavior notes slightly reduces completeness.

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 covers 100% of parameters (agentId). The description's 'by ID' reinforces the schema but adds no new semantic information, such as where to obtain the ID or format restrictions. Baseline 3 is appropriate given high schema coverage.

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 uses the verb 'Get' with a specific resource ('Conversation AI agent') and method ('by ID'). This clearly distinguishes it from sibling tools like ghl_conversation_ai_search_agents (which searches) and ghl_agent_studio_get_agent (which targets a different agent type).

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 you have an agent ID, but does not explicitly state when to prefer this over ghl_conversation_ai_search_agents or other get_agent variants. No exclusions or alternative guidance is provided beyond the 'by ID' qualifier.

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