BinancePortfolioMarginGetCollateralRate

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

With no annotations supplied, the description carries the full behavioral burden and mostly fails to: 'Query' weakly implies a read-only operation, but nothing states permission requirements, whether the endpoint is weighted/rate-limited, or that results are per-asset. Only the core intent is conveyed.

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?

A single short sentence with no wasted clauses, and the resource is front-loaded. It is efficient, though its brevity is partly the reason other dimensions are thin.

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 one-optional-parameter read query with no output schema, the description is minimally adequate but leaves the agent guessing about the response shape (per-asset collateral rates, tiers?) and the account type prerequisite. A sentence on return content or prerequisites would complete it.

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 single recvWindow parameter is fully documented in the schema (100% coverage, including the 60000 limit), so the schema does the work. The description contributes no additional parameter meaning, which is acceptable at this coverage level but adds nothing.

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 pairs a specific verb ('Query') with a specific resource ('portfolio margin collateral rate for assets'), so an agent knows it returns collateral rates within the portfolio margin product. It does not, however, distinguish this from nearby siblings such as BinanceGetCollateralAssetData or BinanceGetBorrowInterestRate, which sound similarly collateral-related.

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?

There is no when-to-use guidance, no prerequisites (e.g. portfolio margin account required), and no named alternative for fetching collateral-tier data outside portfolio margin. The agent must infer from the tool name alone which of the many collateral/margin siblings to call.

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