list_recent

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's 'List recent messages' is consistent but adds no behavioral context beyond what annotations provide. It doesn't clarify ordering (most recent?) or potential rate limits.

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?

Single sentence with no filler words. Efficiently conveys the core purpose.

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 4 parameters and no output schema, the description is too brief. It does not specify sorting order (e.g., most recent first), pagination behavior, or what 'recent' means. For a list tool, more contextual completeness is needed to ensure correct use.

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 only 25% (only 'account' has a description). The description does not explain the meaning of 'limit', 'mailbox', or 'unread_only' parameters. It only implies the mailbox context, which partially helps but does not compensate for the low coverage.

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?

Description clearly states it lists recent messages in a mailbox for a specific account, which distinguishes it from sibling tools like search_emails (which filters) and read_email (single message). The verb 'List' and resource 'recent messages' are specific and unambiguous.

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?

No guidance on when to use this tool versus alternatives (e.g., search_emails, read_email). It does not specify that this is for quick, unfiltered recent messages, nor does it mention limitations like only showing from default mailbox if not specified.

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