tor_exit_check

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

With no annotations, the description partially compensates by disclosing that the check uses a cached list, hinting at staleness. However, it does not detail cache refresh behavior or rate limits, leaving some gaps.

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 short sentences, no redundant information, directly conveys the purpose and key attribute (cached list).

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 check with one parameter and no output schema, the description covers the essential use case. It could mention return type (e.g., boolean) but is adequate given the tool's simplicity.

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 benchmark is 3. The description adds no extra meaning beyond the schema's 'IP address to check,' failing to specify format (e.g., IPv4 vs IPv6) or valid ranges.

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?

Clearly states the tool checks if a specific IP is a Tor exit node, with a specific verb and resource, and hints at its cached nature which distinguishes it from related tools like tor_exit_nodes and tor_exit_details.

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 implies usage via 'Uses cached exit node list,' suggesting it's for quick checks, but does not explicitly state when to use this tool over siblings or mention any prerequisites or exclusions.

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