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

Annotations already declare this as a safe, non-destructive read. The description adds two useful traits beyond them: results are scoped to a single bucket (no cross-bucket listing) and each thread is returned with its draft and latest message. It says nothing about pagination, volume limits, or ordering.

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?

One sentence, front-loaded with the verb and resource, with the scoping constraint and return content packed in without waste. Nothing is redundant with the title.

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?

No output schema exists, so the description's note about returning drafts and latest messages is helpful, but with 5 parameters at 0% schema coverage and no annotations beyond read-only safety, an agent cannot know what 'search' or 'starredOnly' filter on, nor whether result sets are paginated.

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 description coverage is 0% across 5 parameters, so the description carries the burden, yet it only addresses 'bucket' (listing its enum values) and says nothing about 'search', 'starredOnly', or the required 'projectId'/'siteId'. Four of five parameters remain undocumented anywhere.

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 verb and resource ('List outreach threads') plus the scoping dimension (one bucket at a time), and names the four bucket values. It is clearly distinct from siblings like list_prospects or list_outreach_templates, though it never explicitly contrasts itself with them.

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?

The 'in one bucket' phrasing implies the intended usage pattern and the default bucket ('ready'), but there is no explicit when-to-use guidance, no mention of when an agent should prefer review_outreach_reply or list_prospects instead, and no prerequisites stated.

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