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

No annotations exist, so the description carries the full behavioral burden and meets it: it discloses the paywall ($0.004/call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), that no key or sign-up is required, and the endpoint URL. Most importantly it reveals that over MCP the tool returns only the price and URL, not the data - a non-obvious behavior an agent would otherwise only discover after a wasted call.

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?

Three sentences, front-loaded with the purpose before the alternatives and payment mechanics. Every sentence carries needed information - the payment details are essential given the paywall behavior - though the parenthetical payment-rail list is dense and could be trimmed slightly.

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?

No output schema and no annotations, so the description must stand alone, and it does: it explains what data underlies the profile, what the tool actually returns over MCP, and how to get the real data. For a one-parameter paid tool, nothing an agent needs in order to call it correctly is missing.

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% for the single required 'wallet' parameter, so the description has to compensate. It adds useful meaning by stressing 'ONE X1 wallet' (single wallet, X1 chain, distinguishing it from multi-wallet tools), but gives no hint about the expected address format or how the identifier is matched against indexed trades.

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?

States a specific verb-and-resource pair ('Reputation and trading profile of ONE X1 wallet') with the data source ('trades our screener has indexed') and pins the scope to a single wallet. The sibling tools holdings and top_traders are named as the tools for different questions, so an agent can distinguish this from them without opening any schema.

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?

Explicitly routes the agent: use holdings for current balances and top_traders for the cross-wallet leaderboard, leaving this tool for the per-wallet profile. It also warns that over MCP the call returns price and URL rather than data, which tells the agent not to expect a usable result before deciding to invoke.

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