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

The annotations already declare readOnlyHint and openWorldHint, and the description adds valuable behavior: return fields, CC0 licensing, the year-time-window limitation, and a strong warning that returned values are community/attacker-authored and must be treated as data, never instructions. This goes beyond the annotations without contradicting them.

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 five sentences, each earning its place: purpose, return fields, licensing, an exception/alternative, and a safety note. It is front-loaded with the primary action and stays focused, though it could be slightly tightened by moving the licensing sentence later or removing it without losing core selection guidance.

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?

The description is complete for a read-only query tool: it states what it returns, highlights the key limitation, and includes a security caveat. There is no output schema, so the explicit list of returned fields is helpful. The main gap is the lack of explicit note about pagination or large result handling beyond the year limitation.

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%, so the baseline is 3; all parameters already have descriptions in the schema. The description adds a small amount of extra meaning by explaining that 'year' is unsupported and by listing IOC types, but it does not substantially enrich individual parameter semantics beyond what the schema already presents.

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 clearly identifies the action ('Query the TweetFeed API for Indicators of Compromise') and enumerates the return fields, making the tool's purpose concrete. It does not explicitly contrast itself with sibling tools like search or list_recent_iocs, but the broad 'query for IOCs' framing is enough to distinguish it from single-check tools like check_hash and check_ip.

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 useful usage context: it returns matching rows and includes an explicit 'year' unsupported exclusion with a direct alternative (/v1/year HTTP redirect). It does not enumerate when to use this tool instead of sibling search/list tools, so the guidance is strong but not fully exhaustive.

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