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

With no annotations, the description carries the full burden, and it adds genuinely useful behavior: de-fanging normalization of hxxp and [.] notation, and a per-call credit cost. It stops short of describing return shape (list vs grouped, dedup) or how the 500KB limit is enforced, but the normalization and cost disclosures are meaningful.

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?

Two sentences, front-loaded with the extraction scope. The normalization note and cost line each carry distinct value; nothing is redundant.

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 single-input extraction tool with no annotations and no output schema, the description covers what is extracted, from what kind of input, and a normalization caveat. Missing an explicit return-format statement, which matters more since no output schema exists to document it.

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 coverage is 0% and there is one parameter, so the description must compensate. It characterizes the 'text' input semantically as a block of text such as a threat report, log, or email, which tells the agent what to feed in. It adds no format/size hints beyond the schema's min/max length.

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?

States a specific verb (pull/extract) and resource (IOCs), then enumerates the exact artifact classes: IPs, domains, URLs, emails, file hashes, CVE IDs. This distinguishes it clearly from siblings like extract_links, extract_contacts, and extract_data without needing schema inspection.

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?

Gives clear context for when to use it ('a block of text such as a threat report, log or email'), which frames the input domain well. It does not name or exclude any sibling extract_* tool, so there is context but no explicit routing guidance.

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