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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by explicitly stating it 'Never buys access or binds a wallet', which clarifies specific side effects it does not perform and prevents confusion with action-oriented sibling tools.

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?

Two short, front-loaded sentences: the first states the action and target, the second reinforces non-action. Every word earns its place, and the negative clause is high-value disambiguation without redundancy.

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 read-only tool with one optional, well-documented parameter and no output schema, the description sufficiently conveys the returned subject matter (access and bound wallet) and the absence of side effects. It does not detail response structure, but that is not essential for such a simple introspection tool.

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 100% for the single optional agent_key parameter, which already documents its format, origin, security warning, and alternative authorization method. The description adds no parameter-specific detail, so the baseline of 3 applies.

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 uses a specific verb ('Read') and resource ('exchange access and bound wallet'), and explicitly states what the tool never does ('Never buys access or binds a wallet'), clearly distinguishing it from siblings like speedbot_exchange_bind_wallet and speedbot_exchange_award.

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 read-only context is clear and the exclusion of buying/binding actions provides strong guidance about what this tool is not for. However, it does not explicitly name alternative tools or articulate a when-to-use vs when-not-to-use rule beyond the negative clause.

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