Messages Get Conversation

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

Annotations declare readOnlyHint and idempotentHint, but the description discloses no behavioral details beyond a generic 'Delegated Apple domain tool' phrase. It adds zero context about what the tool does, what chat_id refers to, or what the response contains. No contradiction, but no value either.

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?

It is short, but it is under-specified rather than concise: one sentence that restates the tool name and adds generic MCP exposure boilerplate. The sentence does not earn its place because it contributes no meaning.

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 conversation-retrieving tool with 3 params and an output schema, the description should at least say it fetches a message conversation. None of that is present. An agent cannot tell what domain it operates on, what data it returns, or how it relates to other messaging tools, leaving the definition essentially empty.

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%, and the description includes no parameter information. chat_id, limit, and offset are only bare names in the schema without explanations, and the description does nothing to compensate for this gap. An agent must guess the meaning of chat_id and pagination parameters.

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 says it is a 'Delegated Apple domain tool' and restates the tool name, but never states what the tool does. It is essentially a tautology of the name/title and gives no verb or resource.

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 provides no guidance about when to use this tool instead of siblings like messages_get_message, mail_get_thread, or apple_suggest_message_conversations. There is no context, no exclusions, no alternatives.

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