delimit_notify

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

With no annotations, the description carries full burden. It discloses side effects: 'sends a network message via webhook (JSON POST), Slack webhook, or email (SMTP).' It explains the email reply flow and that replies are consumed by sibling tools. However, it does not mention error handling, rate limits, or permissions, which would raise transparency to a 5.

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?

The description is well-structured with headings and bullet points, front-loading the core purpose. It is verbose but necessary given the complexity (11 parameters, multiple channels, draft system). Minor redundancy exists (e.g., channels listed twice), preventing a 5.

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's complexity (11 parameters, output schema exists), the description covers all essential aspects: purpose, usage guidelines, side effects, auto-trigger rule, channel specifics, email context rules, and draft system. It references sibling tools and provides enough detail for an AI agent to decide when and how to invoke.

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 description coverage is 100%, so baseline is 3. The description adds significant context beyond schema parameter descriptions, such as email formatting rules ('Subject: lead with [ACTION TYPE] bracket'), auto-trigger instructions, and draft registration behavior. It does not, however, provide detailed syntax for every parameter, justifying a 4.

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's purpose: 'Send a notification (webhook / Slack / email).' It specifies the verb 'send' and the resource 'notification', and contrasts with sibling tools delimit_notify_routing (configures rules) and delimit_notify_inbox (reads inbound), providing strong differentiation.

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 states when to use: 'when the orchestrator identifies something that requires owner action — outreach reply, deployment decision, approval needed.' It also specifies when not to use: 'for SIEM-class structured streaming (use delimit_siem) or multi-routing config (delimit_notify_routing).' The auto-trigger rule instructs to 'call immediately, never ask,' providing clear decision criteria.

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