hey_bubble_up

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

Discloses that 'custom' requires a date and 'surprise_me' picks random time, but lacks details on side effects, idempotency, or behavior for other slots like 'now'.

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, no wasted words, front-loaded with purpose and key usage instruction.

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?

Tool has 3 parameters and no output schema or annotations. Description explains scheduling slots but does not mention return value or confirmation behavior.

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 has 100% coverage, but description adds meaningful context by explaining slot meanings and the relationship between 'custom' slot and date parameter.

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 'schedule' and explains 'bubble up (reappear)' clearly. It distinguishes from sibling 'hey_bubble_up_if_no_reply' by focusing on general scheduling.

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 explicit usage scenarios for 'custom' and 'surprise_me' slots, but does not explicitly state when not to use this tool versus alternatives like the conditional bubble up.

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