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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral caveat — that message text is third-party content and should be treated as data rather than instructions — but says nothing about ordering, pagination, empty conversations, or auth requirements.

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?

Two short sentences with no filler, and the resource statement is front-loaded ahead of the safety warning. It is efficient, though the brevity comes partly from omitted information rather than disciplined editing.

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 four parameters, no output schema, and no annotations covering auth or return shape, the description should say what comes back (message list, ordering, limits) and how the conversation is identified. The prompt-injection warning is valuable but leaves the operational picture incomplete.

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 coverage is 75% and the three key/auth parameters are documented in the schema itself, so the schema does most of the work. The description implies conversation_id selects the conversation, but adds no format or sourcing details, and conversation_id itself has no schema description.

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 noun phrase 'Messages in one of your conversations' identifies the resource and implies a read, which separates it from list_conversations and send_message, but there is no verb and no explicit statement that it fetches messages by conversation_id. An agent can guess the purpose, but the description never commits to it.

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?

There is no guidance on when to use this instead of list_conversations, get_listing, or any other sibling, and no mention of required auth (agent_key) or how to obtain a conversation_id. Usage must be inferred entirely from the name.

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