hey_screen_by_id

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

Annotations already indicate destructiveHint and idempotentHint. The description adds that reject does not flag as spam and that approval is reversible from HEY UI (but not yet via MCP), providing context beyond annotations.

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?

Four well-structured sentences with key info front-loaded; no redundant words. Efficiently conveys purpose, workflow, and alternatives.

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?

Given the tool has 3 parameters and no output schema, the description covers return format, references sibling tools, and explains the overall process thoroughly.

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?

Input schema has 100% description coverage. The description adds extra meaning: explains destination enum values briefly (e.g., imbox=important mail) and clarifies that reject does not flag as spam, enhancing schema information.

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 clearly states the tool approves or rejects first-time senders by clearance ID, specifies the two actions and their effects, and distinguishes from sibling tools like hey_list_screener and hey_screen_by_email.

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?

Explicitly tells when to use (for first-time senders in Screener), mentions prerequisite tool hey_list_screener to get clearance IDs, and directs to use hey_screen_by_email for senders that have left the screener. Also notes reversibility from HEY UI.

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