Get a conversation

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 safety profile is covered. The description adds genuinely useful non-schema context: required scopes (conversations:read, luca:read), data sensitivity 'full_content', and the note that no idempotency key is needed.

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?

Front-loaded with the outcome sentence, then scannable metadata lines. Slight redundancy between 'Required scopes: conversations:read' and 'Required OAuth scope: luca:read', and the idempotency line is arguably noise for a read operation, but nothing is bloated.

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?

An output schema exists, so return-value detail is not required here. Scopes, sensitivity, workspace override behavior, and idempotency expectations are all present; the only real gap is the absence of routing guidance against sibling conversation tools.

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 67%; workspaceId and workspaceSlug are already documented in the schema, and the description restates their override behavior while adding the 'default workspace configured by environment' context. The required 'id' parameter has no description in either the schema or the description, though its UUID format/pattern makes it largely self-evident.

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?

States a specific verb and resource ('Get a conversation') and adds scope detail ('with messages and lead context'), which distinguishes it from the sibling luca_conversations_list. It stops short of explicitly contrasting with luca_conversations_messages, so an agent must infer the split from names alone.

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 gives the precondition for workspace targeting ('Use workspaceId or workspaceSlug to override the default workspace configured by environment'), but never says when to prefer this tool over luca_conversations_list or luca_conversations_messages. Usage is implied by the operation name rather than stated.

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