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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds genuinely useful context beyond them: results are 脱敏 and 不含密钥, the shape of the returned fields is ID/交易所/名称, and the call is 免费. It does not cover edge cases such as what is returned when no credential is bound, which keeps it 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?

It is a single compact line with the category tag 【账户与额度】 front-loaded, followed by the resource, the masking caveat, the return fields, and the downstream uses. Every clause carries information; the only minor cost is that the sentence is so dense that it reads as a stack of fragments, but none of the text is wasted.

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 zero-parameter read tool, the description is nearly complete: it names the resource, whether the data is safe to expose, the returned fields, and the downstream purpose. Because there is no output schema, the explicit field list (凭证 ID/交易所/名称) is particularly valuable, and the absence of any error or empty-state behavior 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?

The tool takes zero parameters, so the parameter semantics baseline of 4 applies. There is nothing in the description that conflicts with the empty input 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 uses a specific verb and resource: 查询 + 我绑定的交易所凭证, and explicitly states that the returned data is masked and contains no secret keys. An agent can tell this apart from sibling read tools such as platform_positions or platform_account_overview because the resource is clearly named as the exchange API credentials themselves.

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?

It says that the credentials are 供下单、平仓、查询使用, which implies they should be fetched before trading or account operations, but it does not state when to call this tool rather than a specific sibling, nor any preconditions such as having already bound an exchange. This is implied usage only, so it cannot be scored higher than 3.

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