Messages Get Message

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

The annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. However, the description adds no behavioral context such as return shape, message scope, or failure behavior; 'Delegated' is a harness detail, not a behavioral disclosure.

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 not meaningfully concise—it is under-specified. The single sentence repeats the tool name and packaging context instead of explaining behavior or key constraints.

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 an output schema being present, the description lacks even a minimal statement of what the tool does. An agent must infer everything from the tool name and title. For a simple get-by-id tool this is somewhat recoverable, but the definition is not complete enough to support correct invocation in ambiguous contexts.

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 provides no information about message_id. The parameter name and title 'Message Id' imply its role, but the description does not compensate for the missing schema description or clarify format, scope, or expected source.

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 'Delegated Apple domain tool 'messages_get_message' exposed through Apple-Tools-MCP' merely restated the tool name and framework; it does not state that the tool retrieves a message or what message_id identifies. No specific verb or resource behavior is provided.

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 tool instead of siblings such as messages_get_conversation, messages_search_messages, or maill_get_message. No context, prerequisites, or alternativa conditions are mentioned.

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