set_shortlist_alert

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

Describes triggering conditions (percentile_below, delta_below), evaluation schedule (daily baseline refresh), delivery methods (webhook/email), and scope (API key). Adds significant 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?

Front-loaded with purpose, uses bullet-like examples. Slightly verbose with repeated campaign metaphor but overall well-structured and informative.

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 purpose, mechanism, triggering, delivery, and scope. Missing return value but acceptable for a setter. No output schema needed for typical use.

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?

With 100% schema coverage, baseline is 3. Description adds helpful examples (e.g., 'pass a NEGATIVE number, e.g. -8') and context (shortlist from save_to_shortlist). Goes beyond schema.

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?

Specifically states it sets a 'DRIFT ALERT' on a saved shortlist to notify on material standing changes, differentiating it from polling. Includes scope and campaign context.

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?

Clearly explains when to use ('stop polling', 'wake me when it matters'), implies alternative (polling), and ties to long-running campaigns. Does not explicitly name sibling tools or exclusions.

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