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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description goes beyond by explaining auto-detection of IOC type, per-type source coverage (e.g., hash → ThreatFox only), and the presence of sources_queried and sources_unavailable fields to signal what actually ran. No contradictions detected.

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 longer than average but every sentence contributes new information: source coverage, alternative tools, rate limits, and return shape. It is front-loaded with the core purpose, then expands into details, making it efficiently scannable despite density.

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?

This is a multi-source enrichment tool with no output schema to fall back on, but the description covers types, sources, failure handling (sources_unavailable), rate limits, and alternatives. It also mentions the return fields (indicator, type, threat_level, sources, summary, verdict), making it fully self-contained for an agent to select and invoke 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 schema already documents the single 'indicator' parameter with examples, so the baseline is 3. The description adds significant semantic context: auto-detection, per-type source coverage, and the meaning of verdict fields, which clarifies not just the parameter format but how the tool interprets it.

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 opens with a specific verb + resource ('Enrich Indicator of Compromise') and enumerates accepted types (IP/domain/URL/hash). It also explicitly differentiates from sibling tools by naming threat_intel and hash_lookup as alternatives, making its role clear.

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 states when to use this tool ('primary IOC triage tool when type unknown') and when not to, recommending threat_intel for domain-only and hash_lookup for richer MalwareBazaar data. It also provides rate limits (30/hr free, 500/hr Pro), giving concrete context for invocation.

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