twake_mail_mailboxes

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

No annotations are present, so the description bears the full burden of behavioral disclosure. 'List' implies a read-only operation, but the description says nothing about pagination, ordering, system versus user mailboxes, permissions, visibility scope, or the structure of the returned mailboxes.

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?

A single, front-loaded sentence with no filler. Every word contributes to the tool's meaning, and there is no redundant information.

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 zero-parameter listing operation, the description is minimally viable: an agent knows what resource is being listed. However, with no output schema and no annotations, it lacks detail about what each mailbox entry contains, whether all accounts are included, and what the response looks like, so it is adequate but not complete.

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 tool has zero parameters, so the input schema fully defines the parameter surface. The description reinforces that no arguments are needed by saying 'List all', which is sufficient given the empty 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 uses a specific verb ('List') and resource ('all mailboxes/folders in Twake Mail'), making the tool's purpose clear. It does not explicitly differentiate from siblings like twake_mail_inbox or twake_mail_read, but the resource scope is distinct enough for basic selection.

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 about when to use this tool versus alternatives. The description never mentions that this is the folder-listning counterpart to twake_mail_inbox or that it complements twake_mail_read, so an agent receives no routing hints.

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