get_conversation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description does not state whether this is a read operation, whether it opens a new view or returns data, whether it requires an authenticated session, or what it does to the browser/page state. For a tool that 'opens' a thread, the agent can't tell if this returns message content or simply navigates.

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 a single, concise sentence with no wasted words. It front-loads the primary verb and resource. The main structural improvement would be separating the two input methods into clearer guidance, but overall it's efficient.

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 annotations, no output schema, and 0% schema coverage, the description carries the full explanatory burden but provides minimal detail. It doesn't clarify expected return value, whether the tool navigates to a page or fetches data, authentication requirements, or failure behavior. For a messaging tool with two underspecified params, this is insufficient.

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. It explains that index is a 1-based index from list_conversations (adding useful semantics) and that thread_url is an alternative identifier for the thread. However, it doesn't clarify the relationship between the two params (are they mutually exclusive?), which param takes precedence if both provided, or format details for index.

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 states the verb ("Open") and resource (a messaging thread), and distinguishes the two input methods (index from list_conversations, or thread URL). It's specific enough to convey what the tool does, though it doesn't explicitly distinguish from sibling send_message or start_conversation beyond context.

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 tells how to reference a thread (by index from list_conversations or by URL), which implies the workflow dependency on list_conversations. However, it doesn't state when to prefer this over start_conversation or send_message, nor does it explain when to use index vs thread_url. The reference to list_conversations provides useful guidance but no explicit exclusions or alternatives.

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