conversation_ai_get_generation_details

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no additional behavioral context, such as return format, pagination, or any side effects, but since annotations cover the safety profile, it meets the baseline expectation.

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 concise (a single phrase), which is not verbose but also lacks structure and front-loading of key information. It is short enough to be focused, but it omits necessary details, so it balances between being appropriately brief and under-specified.

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?

With no output schema and a very thin description, an agent cannot determine what 'generation details' are returned, what the 'source' enum means, or how to correctly invoke the tool. For a 2-parameter tool with an enum, this is insufficient context to ensure correct usage.

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 50% (only messageId has a trivial 'Message Id' description; source has no description). The tool description does not attempt to clarify parameter meanings or the distinction between source values. Given the low coverage, the description should compensate but fails to, leaving the source parameter ambiguous.

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 'Get the generation details' essentially restates the tool name without adding specificity. It does not explain what 'generation details' refers to or how it differs from other conversation_ai_get_* tools like conversation_ai_get_action_by_id or conversation_ai_get_agent. The purpose is vague and barely goes beyond the name.

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?

No guidance is provided on when to use this tool versus alternatives, nor how to choose between the 'conversation' and 'workflow' values for the source parameter. The description gives no context about the input selection or any prerequisites, leaving the agent without direction.

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