ti_hunt_package

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

With no annotations, the description carries the disclosure burden. It discloses that the tool fuses multi-source data and returns a tracker-ready artifact, which are useful behavioral traits. However, it does not mention performance/cost, whether any external sources are queried live, or any constraints/limitations.

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 substantive second sentence is dense and well organized, but the opening 'ELITE: THE ULTIMATE HUNT TOOL' is hype that does not earn its place. Overall length is appropriate, but not every sentence carries functional 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?

For a complex tool with no output schema, the description gives a useful high-level inventory of returned content and states the intended downstream use. It does not explain how optional parameters log_sources and max_techniques shape the hunt package, nor detail the output structure, leaving moderate gaps.

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 schema already explains all parameters. The description only groups industry/region/scenario as 'client context' and adds no detail beyond the schema; baseline 3 is 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?

The description states a clear, specific verb and resource: 'produce a complete hunt package' from client context, and enumerates distinct deliverables (threat actors, TTPs, coverage analysis, gaps, vendor intelligence). This distinguishes it from sibling tools like ti_actor_full_profile or analyze_coverage, which focus on narrower outputs.

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?

It gives a clear invocation context: when a client context (industry + region + scenario) is available and a full fused hunt package is needed. It does not explicitly name alternative tools or exclusion conditions, so it falls short of full 5, but the trigger condition is unambiguous.

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