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

Annotations already declare readOnlyHint and openWorldHint, so the safety baseline is covered; the description goes further by disclosing the exact returned columns, the CC0 license, the unsupported 'year' window, and a prompt-injection warning to treat field values as data rather than instructions. That last point is meaningful behavioral context an agent would otherwise have to guess, though pagination/rate-limit behavior is still unstated.

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-loaded with the purpose, then return fields, license, the year caveat, and the safety warning — each sentence carries distinct information. Slightly dense at four sentences, and the CC0 licensing note is the weakest contributor, but nothing is padded or 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?

With no output schema, the description correctly compensates by enumerating the returned row fields (date, researcher handle, type, value, tags, tweet URL). It also covers scope, the unsupported window, and a security caveat; only pagination behavior and any auth/rate expectations are left unaddressed.

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 description coverage is 100%, so the schema already documents tag, time, type, user, and limit with examples and defaults — baseline 3 applies. The description adds only one marginal parameter fact: that 'year' is deliberately absent from the time enum because the payload is too large for a tool response.

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 (Query) and resource (TweetFeed API IOCs) and enumerates the value types covered (URLs, domains, IPs, MD5/SHA256 hashes), so the agent knows exactly what comes back. It does not, however, explicitly contrast itself with close siblings such as list_recent_iocs, enrich_ioc, or the check_* tools, so differentiation is left to inference.

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?

It gives one concrete usage boundary — the 'year' window is unsupported and the agent should fall back to the /v1/year HTTP redirect — which is genuinely useful routing information. But it never says when to prefer this tool over list_recent_iocs, search, or get_trending, and there are no stated prerequisites or exclusions beyond the year case.

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