thunder_feel

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

No annotations are provided, so the description carries the full disclosure burden. It implies two outbound network requests but says nothing about safety, side effects, rate limiting, auth requirements, or what the probe reports back.

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?

It is a single front-loaded sentence with no filler, which is good structurally. But the brevity tips into under-specification, leaning on undefined internal terminology instead of explaining the operation.

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?

With no output schema and no annotations, the description is the only source of behavioral information, yet it does not explain what the probe returns (detection verdict? per-mode comparison?) or how the two results are presented. This is a significant gap for a diagnostic 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 coverage is 0% for the single 'url' parameter, and the description provides no compensation: no format, no constraint (e.g., must be absolute, http/https only), and no explanation of whose URL perspective the request originates from.

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 action (probing a URL's bot posture) and distinguishes two modes (plain request vs 'thunder ghost' TLS-true request). However, 'thunder ghost' is undefined jargon that overlaps with the sibling tool thunder_ghost, so an agent cannot fully tell what this tool does differently from that sibling without inference.

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?

No guidance is given on when to use this tool versus thunder_ghost, thunder_challenge, or thunder_open. The description only states what is compared, not the conditions or scenarios that should trigger this probe.

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