Delimit Security Ingest

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

Beyond the annotations, the description discloses concrete behavioral details: writes findings to the ledger, creates new items, optionally closes resolved ones, computes a stable fingerprint for diffing, is gated by require_premium, and returns a specific unlicensed-call error without running. This fully informs the agent of side effects and failure modes.

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 clear sections and front-loaded purpose. It is slightly redundant, repeating the Pro/premium requirement and partially restating sibling contrast, but overall every major section earns its place and the length is justified for the tool's complexity.

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 that an output schema exists, return-value documentation is not required. The description covers when to use, when not to use, sibling alternatives, side effects, prerequisites, and unlicensed behavior. Nothing critical is missing for an agent to select and invoke this tool correctly.

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 the input schema already documents all four parameters thoroughly, including allowed scanner names and auto-detect behavior. The description adds useful high-level context about external scanner JSON output but does not contribute meaningfully beyond the schema for individual parameters.

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 states a specific verb and resource: 'Ingest external security scan output and normalize into ledger findings.' It immediately distinguishes itself from delimit_security_scan and delimit_security_deliberate by naming the exact bridging role it plays, making the tool's purpose unmistakable.

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?

The description provides explicit 'When to use' and 'When NOT to use' guidance, names the alternative tools (delimit_security_scan, delimit_security_deliberate), and explains the sibling contrast. An agent can reliably decide whether to call this tool or a sibling without further inference.

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