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

There are no annotations, so the description carries the full behavioral burden. It only states that the tool monitors marketplaces and paste sites, without disclosing whether it performs live darkweb access, whether a query is needed, what results are returned, or any limitations.

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 very short and front-loaded, but it repeats the tool's name ('Darkweb Monitor' followed by 'Darkweb monitoring'). The mention of 'marketplaces, paste sites' adds some useful scope, but the structure is redundant and underdeveloped.

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?

Even with an output schema and one optional parameter, the description leaves out essential invocation context: what q means, what kind of monitoring output to expect, and how this differs from similar tools. The description is not sufficient for an agent to confidently select and use this tool correctly.

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 only parameter is q, with 0% schema description coverage, and the description never mentions q or what value it expects. An agent cannot determine whether q is a search term, domain, keyword, or optional filter. The description adds no parameter meaning at all.

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 conveys that the tool is about darkweb monitoring and names marketplaces and paste sites as the monitored sources. However, it is largely a restatement of the title and lacks a concrete verb like 'search' or 'look up', so the exact action an agent should take is still vague.

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 overlapping siblings such as breach_aggregator, cryptomarket, paste_domain, or leakcheck. An agent is left to guess which of the many darkweb-related tools is appropriate.

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