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

Annotations already cover read-only/idempotent/non-destructive; the description adds that it returns only metadata + last activity and points to get_thread for bodies. It also discloses a system limitation (no email sending), which is useful context beyond the schema.

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 short sentences, front-loaded with action/resource and immediately useful routing information. Every phrase contributes to selection or invocation, with no wasted words.

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?

Rich annotations plus the description's response-scope note and get_thread routing make this simple two-param tool safely callable. An explicit mention of pagination or what 'metadata' includes would add value, but nothing critical is missing for selection and 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?

Two optional params; the schema describes limit's range/default, and unread_only is self-evident from the name, but the description adds no parameter-level meaning. At 50% schema coverage, this is adequate but does not exceed what the schema already provides.

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?

States a specific action ('List') on a specific resource ('Outreach conversation threads') and defines scope as metadata + last activity, not bodies. It distinguishes itself from sibling get_thread by directing message-body access elsewhere.

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?

Names get_thread as the route for message bodies and explicitly says replying is not available through tools, so an agent knows not to reach for this tool for replies. Caveat: with send_reply present as a sibling, the absolute 'no tool can send email' is confusing and may mislead an agent.

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