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

Annotations declare the tool is not read-only and not destructive, so the mutation safety profile is partly covered. The description adds a useful precondition (thread must be marked won or lost), but it omits side effects such as whether the won/lost status is cleared, whether related automation resumes, and what permissions are required.

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 wasted words. It is efficient, but its extreme brevity leaves no room for structure or supporting detail.

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 three-parameter mutation tool with no parameter descriptions and no output schema, the description is too thin. It gives the purpose and a precondition but does not explain parameter semantics, expected response, or operational side effects an agent would need to call it correctly.

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% for all three required parameters (projectId, siteId, threadId). The description only says 'a thread', which weakly maps to threadId and leaves projectId and siteId entirely unexplained, failing to compensate for the schema's lack of detail.

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 action (reopen) and resource (outreach thread), plus the key condition that the thread was marked won or lost. It clearly differentiates the operation from marking a thread won or lost, though it does not explicitly name sibling alternatives.

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 phrase 'that was marked won or lost' gives an implicit condition for use: reopen a thread only after it has reached a terminal status. However, it does not state when not to use the tool, what to do if the thread is already active, or how it relates to siblings like mark_outreach_won or mark_outreach_lost.

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