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

With no annotations present, the description fully compensates: it spells out exact matching over 365 days, a 30-day substring window fallback with an example, and archive-history flagging that can surface old sightings. It also warns that returned values are community-authored and should be treated as untrusted data, which is essential behavioral safety guidance.

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?

Every sentence in the description earns its place: the main action, the matching/time-window behavior, the security warning, and the input recommendation are all included without redundancy. Critical caveats are front-loaded.

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 low-complexity tool with a single required parameter, the description is complete. It states what the tool checks, how it decides matches, what the caveats are, how to get the best result, and how to handle output safely. The missing output schema is not a concern because the description gives enough behavioral context.

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 input schema already documents the 'ip' parameter with examples, so this is baseline 3. The description adds value by advising 'Pass a full IPv4 / IPv6 string for the best exact-match hit rate,' giving the agent practical guidance beyond the schema.

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: 'Check whether an IP address appears in the TweetFeed corpus.' This uniquely identifies the tool among siblings like check_hash and check_url by scoping it to IP addresses and the indicated corpus.

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 frames a concrete use case: 'Useful for confirming if an observed IP has been flagged as attacker infrastructure' by the infosec Twitter/X community. It does not explicitly discuss alternatives or when-not-to-use, but the context is clear enough that an agent can decide to use this for IP-defender checks.

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