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

With no annotations, the description carries the full burden, and it does disclose a real behavioral trait: a $1.00 USDC charge on Base via x402, which tells the agent this is a paid, wallet-settling call. It says nothing about what data is actually retrieved, how inputs are used, or what the report contains beyond 'structured,' leaving significant gaps for a mutation-free but paid tool.

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 short sentences, front-loaded with the capability and then the price. Nothing is padded and no sentence is wasted.

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 paid aggregate tool with no output schema and no annotations, the description at least establishes the composite nature of the report and the payment requirement. It falls short on how the four identifiers are consumed and how the result differs from sibling scans, but the core contract is present.

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% across four parameters, and the description adds no meaning for email, handle, fullName, or walletAddress. In particular it does not say whether only fullName is needed or whether the optional identifiers sharpen the sweep, so the agent gets no help from prose.

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 names a concrete composite output: public-exposure checking, privacy scoring, and removal guidance rolled into one structured report. That is more specific than a tautology, but it never distinguishes this aggregate from overlapping siblings such as opsec-score, threat-scan, or data-removal, so an agent must infer the boundary.

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 statement of when to pick this sweep over breach-check, opsec-score, or data-removal, and no exclusions or prerequisites beyond the price. The only actionable context given is the payment mechanism, which is a cost notice rather than usage guidance.

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