connect_browser_wallet

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

With no annotations, the description must disclose behavioral traits. It mentions 'switch to browser mode' but does not explain side effects (e.g., disconnects previous wallet, requires user interaction, changes global state). This is insufficient for a connection tool.

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?

One sentence, 13 words, front-loaded with essential action. It is very concise, though it may sacrifice necessary detail. No waste.

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?

Given no output schema, no annotations, and two optional parameters, the description is too minimal. It does not explain what 'browser mode' means, what the result is, or how the wallet address is used afterward. An agent may lack confidence in using it correctly.

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 already provides clear descriptions for both parameters (network enum with default, optional address override). The description adds no additional meaning beyond the schema.

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 clearly states the action ('Connect'), the resource ('browser wallet'), and the additional context ('TronLink-compatible, switch to browser mode'). This distinguishes it from sibling tools like import_wallet or set_active_wallet.

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?

The description gives no information on when to use this tool versus alternatives, such as import_wallet or set_active_wallet. It lacks prerequisites or conditions like 'use this when a TronLink extension is installed' or 'not needed if already in browser mode'.

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