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

Annotations already mark this as read-only and open-world, and the description adds valuable behavioral context: the data window (trailing 30 days), the provenance (AI-clustered), and a security-relevant warning that returned values, including AI-authored summaries, are untrusted and must be treated as data, not instructions. It also discloses alternative download formats. No contradiction with 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 longer than average but every sentence earns its place: the first fronts the core behavior and return shape, the second gives the prerequisite, the third documents alternative formats, and the fourth is a critical security warning. It is well-structured and not bloated.

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?

With no output schema, the description fully specifies the return value: campaign header fields and row fields. It also covers input source, optional filters, limits, alternate download URLs, and untrusted-data handling. An agent has everything it needs to call the tool correctly and interpret results.

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 description coverage is 100%, so the baseline is 3. The description reinforces the meaning of type and limit ('optionally filtered by IOC type and capped by limit') and references get_campaigns for campaign_id, but it adds no technical detail beyond what the schema already provides.

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 and resource: 'Return the full IOC membership of one AI-clustered campaign from the trailing 30-day window.' It then enumerates the exact fields returned and the optional filters, making the tool's scope unmistakable. Although it does not explicitly distinguish from siblings, the campaign-scoped identity is inherently distinct from the other listing/search tools.

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 gives a clear prerequisite ('Get campaign ids from get_campaigns') and states the two optional controls (filter by type, cap by limit). This is clear context for when to call the tool, though it does not explicitly state when not to use it or name alternative sibling tools for different needs.

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