ti_actor_full_profile

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose that the tool fuses multiple sources and performs an optional OTX IOC pivot, which is useful. However, it does not state whether the operation is read-only, whether it makes external network calls, what happens when sources fail, or how results are shaped.

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 compact: one sentence defining behavior and one sentence giving the usage context. It front-loads the core value and keeps the guidance actionable. The 'ELITE CORRELATION:' prefix is mild marketing filler, but it does not undermine clarity or consume excessive space.

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's complexity and the absence of an output schema, the description explains what the profile contains but not its return structure, how the top 20 techniques are selected, or how failures elsewhere (e.g., OTX or vendor blogs) are handled. It is adequate for initial selection but not fully self-sufficient for an agent expecting a precise contract.

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 documents both parameters well. The description adds minor framing by calling the actor a 'named threat actor' and describing include_iocs as an optional OTX pivot, but these mostly restate what the schema already says. This meets the baseline without adding substantial new parameter meaning.

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 uses a specific verb ('Build') and a clear resource ('the most complete threat actor profile available'), then enumerates the fused data sources: MITRE ATT&CK group data, live vendor blog reports, OTX IOC pivot, and detection coverage scores. It is clearly scoped to full actor profiling but does not explicitly name or contrast sibling tools, so it stops short of a 5.

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 explicitly states when to use the tool: 'Use this before any hunting engagement against a named threat actor.' This gives an agent a clear trigger condition. However, it does not provide exclusions or name alternative tools for narrower lookups, so it lacks full routing guidance.

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