list_account_messages

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

No annotations provided. Description mentions ordering ('newest first') and account-wide scope but does not disclose rate limits, required permissions, side effects, or pagination behavior beyond cursor usage. Adequate but not thorough.

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?

Two sentences: the first clearly states core purpose and sorting; the second distinguishes from sibling. No wasted words, front-loaded with key 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?

Given 6 parameters and no output schema, the description covers purpose and usage distinction well. However, it omits details on return format, pagination mechanics (beyond mentioning cursor), and error scenarios, leaving some gaps for effective invocation.

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% with descriptions for all 6 parameters. The description adds no additional parameter-level meaning; it only mentions 'account-wide key' in relation to the sender parameter, which is already clear from 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?

Description clearly states the tool lists messages across all products account-wide, sorted newest first. It explicitly contrasts with list_emails, making the scope 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?

Description provides guidance on when to use this tool vs list_emails: 'Like list_emails but not scoped to one sender — use an account-wide key'. It implies usage context but lacks explicit when-not-to-use or alternative tools for other cases.

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