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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavioral context: per-search cost, x402 payment networks, conditional charging only when records are found, and the implication that an API key changes the payment path. It stops short of describing rate limits or exact return structure.

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?

Two compact sentences: the first describes the returned records, the second covers cost and billing behavior. The result description is front-loaded, and the cost sentence earns its place because it materially affects invocation.

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?

For a read-only, one-parameter, open-world lookup with no output schema, the description adequately explains what comes back and the cost model. However, in a sibling set crowded with username-specific tools, it omits the alternative-selection guidance needed for an agent to choose confidently.

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 100%, with the single username parameter already documented as 'Username or handle'. The description does not add format constraints, examples, or meaning beyond what the schema provides, so the baseline 3 applies.

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 resource: records tying a username to sites and accounts, with associated data. It does not explicitly distinguish this generic lookup from siblings like username_scanner or platform-specific tools such as github_user, so it falls 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?

It provides payment context (x402, $0.25 USDC, charged only on hits) but gives no guidance on when to use this tool versus username_scanner or the many platform-specific username tools. An agent must infer selection from the name and sibling list alone.

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