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

With no annotations provided, the description carries the full burden. It goes beyond a simple 'scan' by detailing what it analyzes and how funding clusters are interpreted (funder sent ETH to many wallets → Sybil ring). This gives meaningful behavioral insight. However, it doesn't disclose potential limitations or side effects, though the operation is evidently read-only; still, the description adds value.

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 three sentences, each adding value: purpose, analysis dimensions, and cluster logic. It is front-loaded with the primary action. It is slightly wordy but still efficient; no filler. The structure is clear and scannable.

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 the tool has an output schema (not shown), the description need not explain return values. It covers the input parameter, the analysis scope, and the detection logic, which is sufficient for an agent to call it correctly. It doesn't mention any prerequisites or edge cases, but for a simple scan tool with one parameter, this is adequate.

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%, so the description must compensate. It does by specifying that the address is a 'Base (EVM) wallet address (0x...)' – adding chain context and format that the schema's bare 'Address' field lacks. This is sufficient for the single parameter, though it doesn't elaborate on validation or example values.

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 a specific verb ('Scan') and resource ('Base wallet') with a distinct purpose: detecting Sybil indicators. It lists concrete analyses (wallet age, transaction patterns, counterparty diversity, funding source) and even describes the cluster-tracing logic, which unambiguously distinguishes it from sibling tools like moltguard_score or moltguard_credential_issue.

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 description implies the use case ('to detect potential Sybil wallets') and gives enough context to know when it applies, but it does not explicitly exclude alternatives or state when not to use it. Since sibling tools serve clearly different functions (credentials, score, etc.), an agent can infer usage, but explicit routing would be stronger.

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