username_sweep

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions it uses 'Sherlock/Maigret', which implies external network access and a standard enumeration approach, but it fails to explain what the output looks like, whether results are returned to the agent or stored, any rate limiting or timeouts, or whether it is a purely read-only operation. The timeout parameter is not disclosed 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?

The description is a single, front-loaded sentence with zero wasted words. It immediately states the action and the method ('via Sherlock/Maigret'). It is appropriately concise for a simple tool, though it sacrifices detail for brevity, which is more a completeness issue than a conciseness issue.

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 no annotations and no output schema, the description is incomplete for a tool with network side effects. It does not specify what 'enumerate' returns (e.g., list of found URLs, account names, or just boolean presence), how long it might take, or what happens if the username is not found. The timeout parameter hints at potential delays but is not explained, leaving the agent without enough context to fully understand the operation.

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%, so the description must compensate. It implies 'a username' likely corresponds to the required 'selector' parameter, but it never explicitly states that selector is the username to search. The 'timeout' parameter is completely undocumented; an agent cannot tell its unit, default, or effect. This is weak compensation for a 2-param 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 description clearly states the tool's purpose: 'Enumerate a username across social sites'—a specific verb ('Enumerate') with a specific resource ('a username across social sites'). It distinguishes itself from sibling tools like 'person_sweep' (which likely sweeps a person's name) and 'phone_lookup' (phone numbers).

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?

The usage is implied: if you have a username and want to check its presence on social sites, use this. However, there is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives, and no exclusions. It doesn't say 'use this if you need to find accounts for a known username' or contrast with 'person_sweep' for full-name searches.

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