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

The annotations already establish that this is a safe read operation (readOnlyHint=true, destructiveHint=false, openWorldHint=false). The description adds useful behavioral context by saying each thread includes its draft and latest message, but it does not explain pagination, ordering, or result limits. With annotations covering safety, this is reasonable but not rich.

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 definition is a single front-loaded sentence that states the action, scope, and return content with no filler. Every clause earns its place.

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 tool with five parameters at 0% schema description coverage and no output schema, this description is too sparse. It helpfully notes that draft and latest message are returned, but it omits what search and starredOnly do, what projectId and siteId represent, and whether results are paginated or ordered.

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%, so the description must compensate for five undocumented parameters. It only restates the bucket enum values and mentions returned content; it does not explain search, starredOnly, projectId, or siteId. This leaves most parameters semantically opaque beyond their names and defaults.

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 states a specific verb and resource ('List outreach threads') and scopes it to one bucket with the four allowed values. It also indicates the returned content includes the draft and latest message. It does not explicitly differentiate from nearby siblings such as get_outreach_sending_dashboard or list_outreach_keywords, so it falls 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?

The bucket values imply that the caller must choose ready, queued, sent, or replied, but the description gives no explicit guidance on when to use this tool versus related tools like get_outreach_sending_dashboard or list_prospects. There are no exclusions, prerequisites, or alternative-routing instructions.

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