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

Annotations already declare readOnlyHint and openWorldHint, so safety of the operation is covered; the description adds genuinely new behavioral context by warning that returned values are community/attacker-authored and must be treated as data, not instructions. It does not discuss rate limits, empty-result behavior, or result caps, so it is not exhaustive.

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?

Front-loads purpose, then accepted inputs, then return format, then routing, then safety. Every sentence carries distinct operational information and none restates the schema or annotations verbatim.

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 one fully documented parameter, an output schema covering returns, and annotations covering safety, the description supplies the remaining pieces an agent needs: input taxonomy, id format for the fetch handoff, sibling routing, and an injection-safety caveat.

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 100% and the single parameter is already described, but the description goes further by enumerating the four accepted input families with concrete examples ('phishing', '#Lockbit', tfc-...) and clarifying that free text matches campaign names/context, plus the id format returned per input type.

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 (search) and resource (TweetFeed CC0 IOC feed), and enumerates exactly what the query accepts: IOC value, tag, campaign id, or free text. It also states the return shape (ioc:/tag:/campaign: ids) and names the sibling tools it defers to, so an agent can place it among the 14 siblings without opening schemas.

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 a clear workflow purpose ('for a document id to pass to fetch') and an explicit routing rule: prefer enrich_ioc, get_tag_info, get_campaigns when available. It stops short of saying when generic search beats the other lookups (query_iocs, list_recent_iocs, get_trending), so the alternative set is only partially covered.

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