Messages List Conversations

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

The annotations already document readOnlyHint and idempotentHint, but the description adds no behavioral information about pagination, ordering, unread filtering, or return behavior. It neither contradicts the annotations nor enriches them.

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 short, but the space is wasted on boilerplate that repeats the tool's name. This is under-specification rather than effective conciseness.

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?

Although the annotations and output schema provide some safety and return-shape context, the description omits the core purpose and any parameter semantics. For a tool that an agent must select among many sibling message tools, this is not complete enough.

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 does not explain limit, offset, or unread_only. An agent has to guess at the meaning of these parameters, especially the string-or-integer union types.

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 only restates the tool's name and says it is exposed through Apple-Tools-MCP. It never says that the tool lists conversations, so an agent cannot derive the actual function from the description.

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 about when to use this tool versus alternatives like messages_search_messages or messages_get_conversation. The description is not misleading, but it provides zero usage context.

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