ghl_conversation_ai_get_generation

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false. The description adds value by listing exactly what data is retrieved (System Prompt, FAQ chunks, etc.) and providing the endpoint URL and OAuth scopes, which are beyond the annotations.

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 mostly concise, listing key facts in a bullet-like format. However, it redundantly repeats the title 'Get the generation details' as the first sentence. The technical details (endpoint, scopes) are useful and appropriately placed.

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 description partially compensates for the lack of output schema by listing the components returned. However, it does not mention error conditions, response format, pagination, or rate limits. Given that it's a read-only retrieval with no output schema, more contextual detail would be beneficial.

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 50%: only messageId has a brief description ('Message Id'), and source is defined as an enum without description. The tool description does not elaborate on parameter meaning, usage, or how to determine the correct source value. It adds no extra semantic value beyond the schema.

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 it retrieves 'generation details' and lists specific components (System Prompt, Conversation history, etc.). It is distinct from sibling tools like ghl_conversation_ai_create_agent which create or modify AI agents, not retrieve generation data.

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 does not explicitly state when to use this tool vs alternatives. While the purpose is clear, there is no guidance on prerequisites or conditions (e.g., when to use this over ghl_conversation_get_message). Implicitly it's for inspecting AI generation internals, but not explicitly stated.

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