Get MIO Messages

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

Annotations already establish that this is a read-only, non-destructive tool, so the description does not need to carry the full safety burden. It adds the pagination behavior, but does not disclose ordering, default folder behavior, or what kind of message data is returned.

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 two short sentences, front-loads the core purpose, and adds the pagination detail without filler. Every sentence contributes something usable.

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 low-complexity read-only list tool with fully described parameters and safety annotations, the description covers the essential purpose and pagination behavior. It could be stronger by distinguishing itself from search-mio-messages and read-mio-message, but nothing critical for invoking it is missing.

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 100%, and the schema already documents count limits, last_id pagination semantics, and folder_id constants with a pointer to get-mio-folders. The description mentions pagination via last_id but adds no meaning beyond the schema.

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 states a specific verb and resource: retrieve MIO messages from a folder. That is clear and distinct from mutation tools like move-mio-message or delete-mio-message, but it does not differentiate this folder-listing tool from search-mio-messages or read-mio-message.

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 gives no explicit guidance on when to use this tool versus search-mio-messages or read-mio-message. 'From a folder' and pagination imply browsing folder contents, but the agent is left to infer that usage rather than being told directly.

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