list_message_chats

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

No annotations provided, so the description must stand alone. It states the tool lists recent conversations but does not disclose how 'recent' is defined, whether it is read-only, or any side effects. The behavior is generally implied by a 'list' operation, but lacks explicit transparency.

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 concise sentence with no extraneous words. Every word is valuable, achieving high 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?

For a simple parameterless list tool, the description is minimally sufficient. However, it lacks details about the output format (e.g., what fields are returned for each conversation) and does not clarify scope (e.g., how many 'recent' conversations). Since no output schema exists, the description should provide more context, but it does not.

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?

Input schema has zero parameters with 100% coverage. The description does not need to add parameter information, and it correctly offers none. Baseline score 3 applies.

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 clearly states the action (list) and the resource (recent iMessage conversations). It is distinct from sibling tools like read_messages (which likely reads specific messages) and search_messages (which searches content).

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 implies usage for browsing recent conversations but provides no explicit guidance on when to use this tool versus alternatives like read_messages or search_messages. It does not state when not to use it.

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