delimit_security_deliberate

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

Discloses key behaviors: gated by require_premium, calls multiple models via deliberation panel, updates ledger items with verdicts. No annotations exist, so description carries the burden; it does so well, though lacks mention of idempotency or rate limits.

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?

Extremely concise and well-organized: single sentence purpose, then structured sections for when to use, when not to, sibling contrast, and side effects. Every sentence adds value with no redundancy.

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 prerequisites (after ingest), side effects, premium requirement, and output schema exists. Adequately complete for an agent to decide correct usage and invocation, though minor details like error conditions are omitted.

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% and each parameter is already described in the schema. The description adds minimal extra meaning beyond what the schema provides, meeting the baseline but not exceeding it.

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?

Clearly states it performs multi-model triage of security findings, classifying them into categories like real risk, false positive, etc. Distinguishes from sibling delimit_deliberate as the security-class variant.

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 specifies when to use (after delimit_security_ingest), when not to use (for ingestion or scanning from scratch), and contrasts with sibling tool. Provides clear, actionable guidance.

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