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

Adds meaningful context beyond annotations: data source provenance (not repackaged public list), return limits, first-seen timestamp, JSON format, and price. Annotations already establish read-only safe operation, so the description need not repeat that. Transparent about what the caller receives.

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?

Compact ~50-word description with all essential information front-loaded: feed nature, IP content, provenance, use case, output limit, format, and price. No filler, each clause adds value.

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 simple list-feed tool with one optional parameter and no output schema, the description covers the main answer: what is returned (IPs, first-seen), volume cap, use case, and cost. Minor gaps are pagination/authentication details, but they are secondary for this tool.

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 documentation covers the single limit parameter fully (1-500, default 200). The description does not mention the parameter, but it does not need to because the schema already conveys semantics. Baseline of 3 applies due to high schema coverage.

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 and resource: returns a feed of recent IPs caught probing honeypot paths. Clearly differentiates from a generic IP tool by emphasizing first-party telemetry and bulk list nature, distinguishing it from sibling threat_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?

Explicitly gives use cases: for blocklists and threat research. Does not mention when not to use or alternative siblings, but the blocklist/research framing strongly implies bulk feed usage rather than single-IP lookup. Clear context but no explicit exclusions.

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