delimit_security_ingest

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

No annotations provided, so description carries full burden. Discloses side effects: gated by require_premium, writes to ledger, creates/updates findings, computes fingerprints. Could elaborate on error conditions but sufficient.

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?

Well-structured with clear sections (purpose, when to use/not use, sibling contrast, side effects). No redundant sentences, all information earns its place.

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 usage, side effects, and contrasts. Output schema exists so return format not needed. Minor gap: no error handling details, but overall complete for a tool with good schema.

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 description adds little beyond schema descriptions. It mentions auto-detect for defaults, which is helpful but not transformative. Baseline 3 appropriate.

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 states 'Ingest external security scan output and normalize into ledger findings (Pro).' This is a specific verb+resource+outcome. Sibling contrast explicitly differentiates from delimit_security_scan and delimit_security_deliberate, so purpose is clear and distinct.

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?

Explicit 'When to use' and 'When NOT to use' sections. Lists supported scanners (Trivy, Semgrep, etc.) and when to use alternatives. Provides clear decision criteria.

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