ti_check_ip

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

No annotations are provided, so the description must convey behavioral traits. It implies a read-only operation via the word 'check', but does not explicitly state non-modification, error behavior, or potential rate limits. The minimal nature provides some clarity but leaves room for ambiguity

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?

The description is a single sentence with the action and target front-loaded. There is no extraneous detail, and it is immediately actionable.

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 lookup with one documented parameter and an output schema available, the description is functionally complete. The main gap is the lack of usage differentiation among siblings, but the tool's simplicity reduces the risk of misuse.

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 schema fully documents the single parameter 'ip' (IPv4 or IPv6 exact match). The description adds no additional meaning beyond the schema, which already covers the format and matching criterion. Baseline of 3 is appropriate when schema coverage is complete.

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 states a clear verb (check), a specific resource (IP address), and the target context (eSentire IP Watch blocklist). It differentiates its purpose from the sibling ti_ipwatch tool, which likely manages the list, by focusing on a single lookup action.

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 no explicit guidance on when to use this tool versus alternatives such as ti_ipwatch or ti_indicators. While the purpose implies a read-only check, it does not state exclusions or preferred conditions, leaving the agent to infer usage context.

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