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

Annotations already convey readOnlyHint=true and openWorldHint=true. The description adds a small amount of context via '1.00 USDC' (likely cost) and 'No financial advice' disclaimer, but it does not describe what the wallet intelligence includes, rate limits, or any side effects. No contradiction with annotations.

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 short sentences, no filler, front-loaded with the core purpose, followed by cost and disclaimer. Every sentence carries distinct information.

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?

The tool is simple (one parameter) and the annotations cover safety/openness, but the description does not specify what 'wallet intelligence' actually returns or when it should be chosen over sibling tools. Adequate for the minimal input schema, yet leaves the output behavior open to interpretation.

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% and the schema fully documents the address parameter with pattern and description. The description repeats 'BSC address' but adds no new semantic detail, matching the baseline for high schema coverage.

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 states the tool is for 'on-chain wallet intelligence for one BSC address', which identifies the resource but not a specific action or output. It is not tautological, but 'wallet intelligence' is vague and does little to distinguish it from sibling tools like native_balance or brief.

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 use this tool versus alternatives is provided. The only contextual clue is that it handles a single BSC address, which is implicit scope rather than explicit usage direction.

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