stealth_check

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It says the tool opens a bot-detector page and returns a report, but does not state whether it navigates the browser, fetches an external page, waits for page load, or what side effects (e.g., navigation history, network requests) occur. The default URL is helpful, but the mechanism and side effects are opaque.

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 extremely short (one sentence), but it omits critical information that would justify its length. It is under-specified rather than concise: it lacks structure, front-loading a single action without context or usage guidance. Every sentence should earn its place, but here the lone sentence fails to earn its place by being incomplete.

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?

Given that there are no annotations, no output schema, and sibling tools that overlap in purpose (stealth_audit, captcha_detect), this description is incomplete. It does not explain the format of the report, whether it modifies browser state, or how to interpret the result. An agent would struggle to use this tool effectively without additional context.

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?

There is only one parameter (url) and the schema description already mentions it is a detector URL with a default. The description adds value by giving a specific default value (https://bot.sannysoft.com/), which is not in the schema's description. With 100% schema coverage and only one param, the description meaningfully supplements the static schema.

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 verb phrase 'Open a public bot-detector page and return a compact report' states an action and a resource, but does not say what the report contains (e.g., bot detection likelihood, headers, fingerprints). It is barely differentiated from siblings like stealth_audit or captcha_detect, which similarly analyze stealth or bot characteristics.

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 provided on when to use this tool versus alternatives (e.g., stealth_audit for a full audit, captcha_detect for captcha presence). The description does not mention prerequisites, typical workflows, or when not to use it.

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