IOC Intelligence

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds significant behavioral context: it reports gathering data from 7 external feeds (listed) and computing a corr_ioc_consensus confidence score. There is no contradiction, and the description enhances transparency beyond annotations.

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 a single sentence containing all essential information: input, output, workflow hint, and subscription requirement. It is front-loaded with the key action and list of outputs. While slightly long due to the enumeration, every part is relevant and no repetition.

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, the presence of a comprehensive output schema, and detailed annotations, the description is nearly complete. It covers the input, output, sources, and usage context. It could mention that it is a read-only operation, but that is already clear from annotations. Overall, it provides enough context for an agent to use it 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?

The input schema has 1 parameter (ioc_value) with full coverage (100%). The description adds value by clarifying that the IOC can be an IP, domain, hash, or URL, and by describing how the parameter is used to generate a dossier. This provides useful context beyond the schema's type description.

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 specifies exactly what the tool does: given an IOC (IP, domain, hash, URL), it returns a complete dossier with threat intelligence, actor attribution, DNS enrichment, infrastructure pivots, and a confidence score. It clearly defines the input and the rich output, and the phrase 'Powers I found this in a log — tell me everything workflows' makes the purpose immediately understandable. It distinguishes itself from sibling tools by focusing on comprehensive IOC investigation.

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 implies the tool is used when you have an IOC and want a full contextual dossier. It mentions a subscription requirement (Purple tier, $11.99/mo) as a constraint, but does not explicitly state when to avoid this tool or what alternatives exist. However, given its specific purpose, an agent can infer when it is appropriate.

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