ti_ipwatch

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly states the return format ('newline-delimited list') and the data semantics ('malicious IP addresses'). It does not discuss list size or truncation, but the schema's max_entries parameter covers that aspect, and the operation is a simple read-style fetch.

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?

Two tightly written sentences with no filler. The first states the action and resource; the second states the return format and intended use. Every sentence earns its place.

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 fetch tool with optional filters, an output schema, and no required parameters, the description covers the source, return format, and common consumption pattern. It does not mention edge cases like empty results or custom output limits, but the schema and output schema fill most of those gaps.

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 contains and max_entries clearly. The description adds no parameter-level detail beyond that, which is acceptable under the baseline for full 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?

The description names a specific resource ('the eSentire IP Watch blocklist') with a clear verb ('Fetch'). The mention of a newline-delimited list of malicious IPs and firewall/WAF use differentiates it from sibling tools like ti_check_ip and ti_indicators, though it does not explicitly contrast them.

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 a clear usage context: the output is 'suitable for pushing into a firewall or WAF blocklist.' This tells the agent when to reach for this tool, though it does not mention exclusions or point to alternatives for single-IP lookups or general indicator searches.

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