delimit_intel_query

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

Description discloses side effects ('read-only'), internal backend call, and parameter coercion. With no annotations provided, the description fully informs the agent about behavioral traits and implementation details.

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?

Structured with clear sections (purpose, when to use, when not, sibling contrast, side effects, implementation). Front-loaded, every sentence adds value, no redundant information.

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 presence of output schema and only 3 optional parameters, the description covers all essential aspects: usage boundaries, side effects, and internal mechanics. No gaps identified for this read-only search tool.

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?

Input schema already describes all 3 parameters with 100% coverage. Description adds little beyond reinforcing the search dimensions (keyword, date, dataset). The coercion detail is minor; overall, description does not significantly enhance parameter semantics beyond the schema.

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 clearly states 'Search saved intel snapshots by keyword, date, or dataset.' It specifies the resource (intel snapshots) and action (search), and distinguishes from sibling tools like delimit_intel_snapshot_ingest.

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 provides when to use (to surface ingested intel matching a query, optionally scoped to one dataset) and when NOT to use (to ingest new data or list datasets), with specific sibling names. This leaves no ambiguity for the agent.

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