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

Annotations already establish read-only and open-world behavior, and the description adds important context: no API key required, x402 payment, $0.10 USDC per successful call, and supported chains. It does not explain payment failure behavior, rate limits, or x402 flow details, so it is strong but not fully transparent.

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 core capability is front-loaded and the text is dense with useful detail rather than filler. The platform list and pricing note are compact and each serves a clear purpose.

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?

With no output schema, the description usefully enumerates the returned data: platform existence, public profile fields, and mention counts. It leaves some details unspecified, such as response structure and behavior for absent platforms, but it is sufficient for an agent to understand the call's output and cost.

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 one required username parameter and schema description coverage is 100%, so the schema already carries parameter semantics well. The description does not add format details beyond the schema's 'with or without the @' note, making the baseline 3 appropriate.

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 states a specific resource (one username), the exact platform set, and the aggregated result fields. The 'at once' framing distinguishes it from platform-specific lookup siblings, though it does not directly compare to the similarly scoped osint-username sibling.

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?

Usage is implied by the cross-platform 'at once' scope, suggesting it is for aggregate username checks rather than per-platform lookups. However, the description names no alternatives and gives no explicit when-to-use or when-not-to-use guidance.

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