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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses sort order (newest activity first) and that unread counts are included, but it does not mention pagination behavior or limit semantics; "List" implies read-only but the safety profile is not explicitly stated.

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 front-loaded sentence with no filler: verb, resource, ordering, and key returned metadata are all stated efficiently.

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 simple list tool with an output schema, the description covers purpose, ordering, and unread counts. However, with no annotations and no schema descriptions, it leaves the limit parameter and any usage distinction from message_thread unaddressed.

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?

There is one optional limit parameter with 0% schema description coverage, and the description never mentions limit, its default of 30, or its maximum of 100. It adds no meaning beyond the raw schema for the only parameter.

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, "your conversations", and adds useful scope detail: newest activity first with unread counts. It does not explicitly distinguish itself from siblings like message_thread, so it stops short of a 5.

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?

It implies listing conversations but gives no explicit when-to-use guidance, no exclusions, and no comparison to message_thread or message_send. The agent must infer that this is the inbox-listing tool from the name and sentence alone.

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