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

With no annotations, the description carries the full burden; it usefully discloses the engine (Maigret) and that the sweep covers 250 sites and extracts names/emails/phones, hinting at cost and PII sensitivity. It omits whether the scan is slow/rate-limited, whether it requires auth, and any caveats about partial or failed site checks.

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?

One dense, front-loaded line that names the tool, the scope, the engine, and the payoff. It wastes no words, though it is arguably too terse to be instructional.

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 values need not be re-explained, but the sole input parameter is undocumented and there is no sibling differentiation or usage context — leaving real gaps for an agent operating among many username-related tools.

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 schema has one parameter 'q' at 0% description coverage, and the description never mentions it or explains the accepted input format (bare handle vs. URL vs. case sensitivity). The agent must infer from the title that 'q' is the username.

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 (profile dossier) plus resource (250 sites) and names the underlying engine, Maigret, with what data is extracted. However it does nothing to distinguish itself from the sibling 'username' tool, leaving the agent to guess which to pick.

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 guidance, no mention of prerequisites, and no reference to the sibling 'username' or any other username-lookup alternative in a list of hundreds. The agent gets no routing information at all.

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