check_threat_intel

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

No annotations are provided, so the description carries the full burden. It discloses a safe offline fixture fallback, implying reliability. However, it does not mention if the tool is read-only, whether it may hit external APIs, or any latency implications.

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 one clear sentence, front-loading the primary action and key detail about fallback. No wasted words. Could slightly improve by adding context about parameters.

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 the tool invokes an external database query with fallback, has 2 parameters (one unexplained), and an output schema exists, the description is adequate but incomplete. It should clarify the return value (the output schema may help, but it's not referenced).

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 0%, meaning the schema provides no descriptions. The description only mentions 'file_hash' implicitly (says 'for a file hash') but fails to explain the purpose of 'case_id' or its default value. This is a significant gap.

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 queries threat intelligence databases for a file hash, and mentions a safe offline fixture fallback. The verb 'queries' and resource 'threat intelligence databases' are specific. However, it does not differentiate from the sibling 'scan_iocs', which may also query threat intel.

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?

No guidance is provided on when to use this tool versus alternatives like 'scan_iocs'. The description does not state prerequisites, context (e.g., only for certain hash types), or when to avoid it.

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