getCollateralInfo

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to restate safety. It adds useful context about the returned fields, but it does not disclose behavior such as how the optional currency affects results or any account prerequisites. No contradiction with annotations.

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?

The description is one focused sentence that front-loads the core purpose and provides concrete examples of returned data. The trailing 'etc.' is slightly vague but does not undermine the overall clarity.

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 simple read-only tool with one parameter and no output schema, the description is decent but incomplete: it fails to explain the currency parameter's role and optionality. The absence of any parameter guidance makes it harder for an agent to invoke the tool correctly in all cases.

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 schema contains only a bare 'currency' string property with 0% schema description coverage, so the description carries the full burden of explaining parameter meaning. It never mentions the currency parameter, leaving the agent to guess whether it is a filter, required for certain currencies, or optional.

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 a specific verb ('Get') and resource ('collateral information of the current unified margin account'), and lists concrete data points such as loan interest rate, loanable amount, and collateral conversion rate. This distinguishes it from broad sibling tools like getAccountInfo or setCollateralSwitch.

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 implies usage when a caller needs collateral details for a unified margin account, but it provides no explicit guidance on when to choose this over related tools such as getTieredCollateralRatio or getSpotMarginTradeCoinState. There are no exclusions or alternative references.

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