twake_mail_inbox

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

With no annotations provided, the description is the sole safety signal. 'List' implies a non-destructive read operation and 'recent' implies a time-based ordering, but it does not disclose auth requirements, pagination, or whether the listing modifies read/unread state. This is adequate for a simple read-only tool but leaves behavioral gaps.

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 compact sentence that leads with the verb and resource. There is no filler or redundant repetition of the tool name, making it appropriately concise and front-loaded.

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 one-parameter list tool, the core operation is clear, but there is no output schema and no mention of what each returned email entry contains or how results are ordered beyond 'recent'. It does not state whether this tool is meant to provide summaries that lead into twake_mail_read, which leaves the overall workflow slightly underspecified.

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?

The only parameter, limit, is fully documented in the input schema with type and default ('Max emails (default 10)'). Schema description coverage is 100%, so the description adds no additional parameter nuance. Baseline 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 uses a specific verb and resource: 'List recent emails from Twake Mail inbox'. It clearly distinguishes itself from sibling tools like twake_mail_read (which presumably reads a single email) and twake_mail_mailboxes (which lists mailboxes), by targeting the inbox and the listing operation.

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 choose this tool over alternatives such as twake_mail_read or twake_mail_mailboxes. The description implies usage for inbox listing but does not explain when not to use it or what sibling tool to prefer for other scenarios.

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