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

While annotations already declare readOnlyHint=true and destructiveHint=false, the description adds meaningful behavioral details beyond them: it returns every message in the conversation, ordered oldest first, and includes sender and timestamps. This supplements the safety profile with concrete return characteristics, though it does not mention pagination or full message content details.

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 sentence, front-loaded with the primary verb and resource, and packs essential details (scope, ordering, output fields) without any wasted words. It is highly concise and structured for quick comprehension.

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 simple tool with one parameter and no output schema, the description provides sufficient context: it states the operation, the scope (one conversation), the ordering, and the included fields. The only minor gap is that it does not explicitly state whether full message bodies are returned, but for a read-only fetch, this is relatively complete.

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?

The schema already provides 100% coverage with a description for conversation_id ('Conversation ID (UUID)'). The tool description does not add any extra meaning about the parameter, so it stays at the baseline of 3 for high schema coverage. No additional semantic help is offered beyond the schema.

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 uses a specific verb ('Get') and resource ('every message in one inbox conversation'), and clearly distinguishes from sibling tools like list_inbox_conversations (which lists conversations, not messages). It also specifies ordering and fields (oldest first, with sender and timestamps), which unambiguously states the tool's function.

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 clearly implies when to use it: when you need all messages from a specific conversation. It does not explicitly name alternatives or exclusions, but the purpose is so specific that an agent would infer the appropriate context relative to siblings like list_inbox_conversations or categorize_inbox_emails. No misleading guidance is present.

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