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

Annotations cover readOnlyHint and openWorldHint, but the description goes well beyond: the 365-day exact-match window, the 30-day fallback, pre-365-day archive flagging, case-insensitive matching, and an explicit prompt-injection warning about returned field values. This is unusually rich behavioral disclosure.

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 the core purpose and each clause earns its place, but there is mild redundancy ("exact match" appears twice) and the fallback/archive detail is dense. Still 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?

For a single-parameter read-only lookup with no output schema, the description covers search scope, temporal windows, matching semantics, and a security caveat. Nothing an agent needs to invoke it correctly is missing.

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 parameter is already documented (32/64 hex, case-insensitive, INVALID_PARAMS on error). The description adds the auto-detection mechanism (length-based type inference), which is genuinely supplemental rather than restated.

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 (check) plus resource (file hash) and names the exact corpus searched (TweetFeed). It is clearly distinguishable from siblings check_ip, check_url, and query_iocs, which target different resource types.

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 concrete use case (confirming whether a binary sample has been shared by the public infosec Twitter/X community), which tells an agent when the tool is relevant. However, it never explicitly names alternatives or states when NOT to use it versus check_ip/check_url/enrich_ioc.

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