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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, yet the description still adds real value: the verification mechanics (public address with signed message or dust transfer, xpub linking), the hard security constraint 'Never ask for a private key or seed phrase', and what happens when blocked_request is set. The closing 'Read-only: it does not move, sell, convert, or hold crypto' partly restates the annotations, which keeps it just 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?

Front-loaded with the core action and the sibling disambiguation, then layered with workflow and safety guidance in a logical order. The opening sentence is dense with a long enumeration, and the final read-only sentence is largely redundant with the annotations, so it is efficient but not airtight.

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 values need not be described, and the annotations plus description cover safety, workflows, and the security constraint well. The gap is that the realscore_report workflow option is left unexplained even though the sibling generate_realscore_report exists, leaving one enum path unmapped.

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 is 3; the description earns above that by explaining intent for the key params — 'Pass what the conversation has established (target_price_usd, asset, workflow)' and the precise conversational trigger for blocked_request. The only soft spot is that the schema's fourth workflow enum value (realscore_report) is never mentioned in either the description or the schema's own workflow text.

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 concrete verb and resource ('Opens the RealOpen panel beside the current conversation') and immediately disambiguates from the sibling open_realopen by naming it and the difference (panel vs. full-screen sidebar app). It also enumerates what the panel shows, so an agent knows exactly what content this call surfaces.

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 rules: use open_realopen for the full-screen app, use workflow "verify_wallet" to guide wallet verification, and set blocked_request when the user asks to transfer, send, sell, trade, convert, or hold crypto. The trigger conditions and the alternative tool are both spelled out rather than implied.

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