hey_remove_reply_later

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

No annotations provided; description discloses mutation behavior (removing, moving back) and required input source. Clearly states consequence 'mark as Done, moving back to Imbox'.

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 and effect, no wasted words. Critical information (requirement) included efficiently.

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 single-parameter tool with good schema coverage and no output schema, description covers purpose, effect, and parameter source. Could mention side effects (e.g., thread moved back to Imbox) but adequate.

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 already describes posting_id with 100% coverage. Description adds value by specifying the source 'from hey_list_reply_later', clarifying how to obtain the ID.

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 uses specific verb 'remove' and resource 'Reply Later', explains effect ('mark as Done, moving back to Imbox'), and distinguishes from siblings like hey_reply_later and hey_list_reply_later.

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?

States when to use (to remove from Reply Later) and prerequisite (posting_id from hey_list_reply_later). Doesn't explicitly mention when not to use, but the action is well-defined.

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