resume_thread

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

Describes side effects: posts a message and brings thread to top as unread. Discloses the message requirement (explain why now is a good time). However, no mention of permissions or prerequisites, and a schema error (message ref) might confuse. With no annotations, this is fairly transparent.

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 sentences, front-loaded with action, no wasted words. Efficient and direct.

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?

Covers action, side effects, and message content requirement. Lacks explanation of return value and does not address the schema error. Still largely complete for the tool's purpose given no output schema and low schema coverage.

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 coverage is 0% (no param descriptions). Description explains 'message' must contain a reason, but not its format. 'thread_id' is not explained. Adds some meaning but not fully compensatory for both parameters.

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?

Description clearly states the action: un-defer a parked thread and post a message. It specifies the purpose (recommending user to pick up now) and the effect (brings thread to top as unread). Distinguishes from siblings like reopen_thread, create_thread, and defer_thread.

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?

Implies usage when a thread is parked and a blocker is cleared, but no explicit when-to-use or when-not-to-use compared to siblings. No guidance on alternatives like reopen_thread or defer_thread.

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