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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), so the description's job is to add what they don't say — and it does, disclosing a 0.010 USDC cost on Base and Solana Mainnet, i.e., a paid, cross-chain call. It omits payment mechanics (how the fee is settled, prerequisites if unpaid), which is why it falls short of a 5.

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 dense sentences: purpose and outputs first, cost second. No filler, and the highest-value constraint (price) is placed where it will be seen.

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-value detail is unnecessary, and the single parameter is fully documented in the schema. The remaining gap is substantive, though: the wallet-vs-token-address discrepancy means an agent could pass the wrong kind of address with no way to resolve it from the definition.

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%, so the baseline would be 3, but the description actively conflicts with the schema by describing the input as a 'wallet address' when the sole parameter is a token contract address / SPL Mint. That is not just silence but a misleading characterization of the only parameter, so it scores below baseline.

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 specific verb ('Profiles') and enumerates concrete outputs (token balances, USD valuation, historical win-rate, drainer/OFAC taint), which is more than a tautology. However, it says the target is a 'wallet address' while the schema requires a 'token_address' (ERC-20 contract / SPL Mint), so the agent cannot be sure what resource is actually being profiled. That internal ambiguity keeps it at minimum-viable rather than clearly differentiated from the audit siblings.

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?

No guidance on when to choose this over siblings such as rugshield_pre_swap_scan, check_honeypot, or analyze_liquidity, nor any when-not conditions. The only contextual statement is the price, which tells the agent nothing about tool selection.

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