get_conversation_context

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

With no annotations provided, the description carries full burden but only hints at formatting ('agent-friendly') without explaining what that means structurally. Doesn't disclose if this is read-only, cached, or rate-limited, and fails to leverage the existing output schema to describe return value structure.

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?

Single sentence of nine words that front-loads the essential value proposition. No filler or redundancy.

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?

Despite having an output schema and three parameters with zero schema documentation, the description provides minimal context. It doesn't describe the return structure, explain what constitutes 'recent' history, or clarify the 'agent-friendly' formatting.

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 has 0% description coverage, yet the description only loosely alludes to parameters ('recent' hints at messageLimit, 'summary' hints at detailLevel) without explaining constraints, enum meanings (compact vs. full), or the conversationId format requirements.

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 tool returns a conversation summary and message history, specifying the resource (conversation) and output format (agent-friendly). However, it doesn't explicitly differentiate from sibling 'search_conversations' regarding when to use retrieval vs. search.

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 provided on when to use this tool versus 'search_conversations' or 'list_unread_guest_threads'. No prerequisites mentioned for the required conversationId parameter.

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