delimit_siem

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

With no annotations, the description provides adequate behavioral detail: it discloses that configure/forward/test actions involve network writes, while status is read-only. This goes beyond basic purpose but could be more exhaustive (e.g., mention idempotency or error behavior).

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?

Five concise sentences, no redundancy. Front-loaded with purpose, then usage guidelines, sibling contrast, and side effects. Every sentence adds value.

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 an output schema exists, the description adequately covers purpose, usage, side effects, and parameter context. It could include a brief example of a typical usage flow, but is otherwise complete.

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%, so baseline is 3. The description adds minimal parameter-level detail beyond what the schema already provides (e.g., example integrations), but doesn't significantly enhance understanding.

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 manages SIEM streaming for audit-event forwarding, specifies supported endpoints (Splunk, Datadog, etc.), and distinguishes from sibling tools like delimit_notify and delimit_notify_inbox by contrasting purpose.

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 (inspect/configure streaming) and when not to use (one-shot notifications, inbox handling), with direct references to alternative tools. The sibling contrast further clarifies usage boundaries.

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