postCryptoLoanCommonMaxLoan

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

Despite no annotations, the description discloses that the endpoint is private (requires authentication), has a rate limit of 5 per time window, considers VIP level and existing borrowed amounts, and returns 0 if insufficient. This is good behavioral transparency for a mutation-like calculation tool.

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?

Well-structured with sections (Features, Use Cases, Important). Every sentence adds value, no redundancy. Front-loaded with the core purpose. Efficient and clear.

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?

The description covers auth, rate limit, return values (currency amount and USD notional), and edge case (returns 0). Although no output schema, the return format is mentioned. It is complete enough for an agent to make an informed decision.

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?

While schema coverage is 0%, the description explains that 'currency' is the loan currency and 'collateralList' is a list of collateral items with currency and amount. Features and use cases reinforce that the collateral list affects the max loan calculation, adding meaning beyond the property names.

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?

Description clearly states the tool calculates the maximum borrowable amount for a specific currency based on provided collateral. It distinguishes from siblings like getCryptoLoanCommonMaxCollateralAmount by focusing on loan amount rather than collateral.

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?

Provides explicit use cases such as checking borrowing capacity before creating a loan order and validating collateral sufficiency. Does not explicitly mention when not to use or alternatives, but the use cases are clear and practical.

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