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

With no annotations, the description carries the full burden but discloses only that this is an external API call ('via HudsonRock Cavalier free API'). It does not state what query types are accepted, whether results are raw logs or verified exposures, rate limits, or false-positive caveats. The external-call hint is useful context but far from sufficient for a third-party intelligence lookup.

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 a single compact sentence that front-loads the key purpose. The leading 'HudsonRock Stealer:' prefix is mildly redundant with the tool name/title, but it adds the 'Stealer' framing in just two words, so the waste is minimal.

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?

An output schema exists, so return-value documentation is not required, but the description is incomplete for correct invocation: the input semantics of q are unknown, the relationship to close sibling tools is unstated, and the behavioral profile is thin. An agent cannot reliably select or call this tool based on what is provided.

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 0% and the description adds nothing about the sole parameter `q`. An agent cannot determine whether q expects an email, domain, IP, username, or hash — a critical unknown for stealer-log lookups, where query type typically selects the endpoint. Optionality (default '') also goes unexplained, e.g., what happens when the tool is called with no query.

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 identifies a specific niche and action: checking for stealer-log exposure via HudsonRock Cavalier. 'Stealer-log exposure check' names the resource and the implied verb (check) unambiguously enough to distinguish the domain. However, it does not differentiate from the numerous breach/leak siblings (leakcheck, breachdirectory, breachdb, credential_stuffing), so it stops short of a 5.

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 when-to-use or when-not-to-use guidance. The sibling list contains many close substitutes in the leak/breach space (leakcheck, leaklookup, breachsearch, dehashed_domain, password_dumps, darkweb_monitor, hibp_email), and this description gives an agent no basis for choosing hudsonrock over any of them.

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