chatwoot_get_conversation

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. However, the description adds almost no behavioral context beyond that: it does not mention output_format behavior, whether 'full details' means all fields, any access requirements, or how errors are surfaced. This is minimal additional transparency.

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 main sentence is front-loaded and appropriately brief, but the Args block is mostly redundant with the input schema. It is not bloated, yet it is under-specified: the lines add bulk without adding information that helps an agent invoke the tool correctly.

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 an output schema present, return-value details are not needed, and the simple two-parameter interface keeps complexity low. However, the description lacks usage context, parameter semantics, and any differentiation from the large sibling list, so an agent would not know when to call this tool versus nearby alternatives.

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 0%, so the description must compensate. The Args section only restates the schema titles ('conversation_id: Conversation ID', 'output_format: Output format') without adding any real meaning. It does not explain what a conversation_id refers to, where to obtain it, or what the markdown/json output formats actually produce.

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 identifies the action ('Returns') and the resource ('a specific conversation'), which is enough for an agent to recognize this as a get-by-ID operation. The phrase 'full details' is somewhat vague and does not explicitly distinguish this from siblings like chatwoot_get_conversation_messages, but it is still specific enough to be functional.

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 choose this tool over its many siblings such as chatwoot_get_conversation_messages, chatwoot_get_conversation_traffic, chatwoot_list_conversations, or chatwoot_search_conversations. The description only states what the tool returns, not the conditions or context in which it should be used.

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