cloak_detection_test

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

No annotations are supplied, so the description carries the full burden. It does not disclose that this makes live requests to third-party probe sites, that results may be blocked or require waiting, or what 'key result fields' actually contains. The only side-effect hint comes from the schema's note that sannysoft is 'free, no captchas', which implies other suites are heavier but is not surfaced in the description.

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?

A single efficient sentence, front-loaded with the action and resource, with no filler or repetition.

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 annotations and no output schema, the description is the only source of behavioral and return-value information, and it supplies almost none. An agent cannot tell what fields come back, whether the call is slow, or whether third-party network egress is involved.

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% and the enum lists all five probe types with a default noted, so the schema already does the parameter work. The description adds nothing about suite or customUrl semantics, so baseline 3 applies.

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: loading a known bot-detection probe page and dumping its key result fields. That is far more informative than the tool name alone, but it does not distinguish itself from the sibling cloak_stealth_audit, which an agent could easily confuse it with.

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?

There is no explicit when-to-use, when-not-to-use, or alternative named. The description implies a bot-detection testing context but never says whether this is for validating a fingerprint configuration versus auditing one's own setup, nor how it relates to cloak_stealth_audit.

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