wallet_profile

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

No annotations exist, so the description carries the full burden and does so unusually well: it discloses the paid pricing model ($0.004/call via x402), accepted payment assets, that no key or sign-up is required, and critically that 'Over MCP this tool answers with that price and URL, not the data.' That last point is a non-obvious behavioral trait an agent could never infer from the schema.

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?

Front-loaded with the purpose, then alternatives, then payment mechanics — a logical order with no filler sentences. The payment parenthetical is dense but each clause is load-bearing; minor tightening is possible.

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 tool with no annotations and no output schema, it covers purpose, alternatives, cost, payment routes, and the MCP-returns-price-not-data quirk. The one omission is what the returned 'reputation and trading profile' actually contains, which an agent would want to know.

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?

There is one parameter with 0% schema description coverage, so the description must compensate. It clarifies the parameter identifies a single wallet ('ONE X1 wallet') sourced from indexed trades, but it never specifies the identifier format (address vs. name), leaving a real gap.

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 — 'Reputation and trading profile of ONE X1 wallet' — and scopes it to 'trades our screener has indexed'. It explicitly names the sibling tools it is not (holdings for balances, top_traders for the leaderboard), so an agent can distinguish it 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?

Gives explicit routing: 'For its current balances use holdings; for the leaderboard across wallets use top_traders.' Both the alternatives and the conditions that select them are stated, leaving nothing to inference.

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