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

Annotations already declare readOnlyHint=true, covering the safety profile. The description adds value by enumerating the returned fields (asset, units, owner address, activity history), which matters since no output schema exists, but says nothing about pagination, ordering, or empty results for a 'returns all' operation.

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 tightly written sentences with the scope constraint front-loaded and zero filler; every clause carries 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?

With one documented parameter, no output schema, and readOnly annotations, the description is nearly complete because it enumerates the returned fields. It leaves pagination/ordering behavior unspecified for a list operation, which is the only real gap.

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 documents the asset parameter with format examples ('BTC~BTC'). The description adds no syntax or format detail beyond what the schema provides, so the baseline 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?

States a specific verb (Returns/list) and resource (trade accounts) scoped to a specific trade asset. It is distinguishable from singular siblings like get_trade_account, though it never explicitly contrasts itself with list_trade_units.

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 scoping phrase 'for a specific trade asset' implies the usage context, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as get_trade_account or list_trade_units.

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