hey_ignore_thread

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

No annotations, but description discloses that thread stays in inbox, is reversible, and returns {success, error?}. Lacks details on permissions or side effects, but sufficient for a mute operation.

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?

Three sentences with no wasted words. Covers purpose, reversibility, return value, and alternatives 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?

Simple tool with one parameter and no output schema. Description sufficiently covers all aspects: what it does, state of thread, reversibility, return value, and when to use alternatives.

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 100% for the single parameter 'posting_id'. Description adds no extra meaning beyond what schema already provides ('The posting ID to ignore'). Baseline score maintained.

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?

Clearly states verb 'mute', resource 'thread', and effect 'stop receiving notifications'. Distinguishes from sibling tools hey_trash, hey_spam, and hey_unignore_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?

Provides clear context for when to mute, and explicitly mentions alternatives for removal (trash) and unsolicited mail (spam). Does not explicitly state when not to use, but alternatives cover main cases.

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