conduyt_get_conversation

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

With no annotations, the description must carry the behavioral burden. It does usefully state the required permission ('communications:view') and describes the returned content, but it does not clarify pagination behavior or whether reading affects the unread state, which are important behavioral traits for a conversation-read tool.

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 three efficient sentences: purpose and contents first, then the follow-up use case, then the permission requirement. Every sentence adds useful information without repetition.

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 tool with no annotations and no output schema, the description covers the main purpose, return contents, primary use case, and required permission. It is nearly complete, though it could mention pagination or explicitly confirm that reading does not mark messages as read.

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 100%, so the schema fully documents all five parameters including around, cursor, channel, and per_page. The description adds no parameter-level meaning beyond the schema, which is the baseline case for high-coverage schemas.

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 states a specific verb and resource: 'Read the full conversation thread for one contact', and clarifies the scope as chronological SMS/email history including inbound and outbound messages plus state, unread count, and notes. This scope separates it from a generic message-list sibling such as conduyt_list_messages.

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?

It gives a clear use case: 'Use this to see what a contact has replied before deciding how to follow up.' However, it does not explicitly name alternatives or say when not to use this tool, so it lacks full routing guidance.

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