x_api_get_chat_conversation

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

With no annotations, the description fully discloses behavior: it declares 'Risk: read-only,' lists required OAuth scopes and token types, explains environment-selection behavior for tenant principal resolution, gives an expected response shape, enumerates common failure conditions, and includes a safety warning about sensitive account data. This goes well beyond basic hints.

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 structured with clear labeled sections and is reasonably concise given the complexity. The main redundancy is 'Use when: Get Chat Conversation,' which duplicates the opening sentence. Otherwise, every section adds useful context without excessive fluff.

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?

For a read-only GET tool with 7 parameters and no output schema, the description covers prerequisites, environment selection, expected response shape, failure conditions, and safety. It doesn't define what a chat conversation is in this API context, but overall it's quite complete for an agent to invoke the tool successfully.

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 0%, but the description adds meaningful semantics for id, scopeTenantId, scopeUserId, scopeAccountId, and credentialKey. It explains the auth resolution rule ('scopeTenantId plus exactly one of scopeUserId or scopeAccountId') and the role of credentialKey. However, authorizationKey and preferredAuthType are not explained, leaving some gaps.

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 opens with 'Get Chat Conversation,' which is a clear verb+resource but essentially restates the tool name. It doesn't explicitly distinguish from the sibling 'x_api_get_chat_conversations' (plural) or describe what a chat conversation is, though the singular form implies a single conversation retrieval.

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 'Do not use when' section provides exclusions (auth/configuration tools, exploring) and recommends x_schema_discovery or x_query_suggestion first. It also lists recommended prerequisite/follow-up tools, but the 'Use when' section is tautological ('Get Chat Conversation') and doesn't clarify when to use this over the plural variant or x_api_request.

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