getCryptoLoanCommonPosition

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

With no annotations, the description carries full transparency burden. It discloses that it's a private endpoint (auth required), rate limit (5 req/UID), returns empty if no loans, and distinguishes flexible/fixed debt. Missing explicit statement that it is read-only, but implied.

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 well-structured with headings (Features, Use Cases, Important) and front-loads the purpose. It is slightly verbose but each section adds value. No wasted words.

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?

Given no output schema, the description covers features, use cases, and important notes. It effectively describes what the tool returns (position metrics, breakdowns) but lacks explicit return format details. Still adequate for understanding.

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?

There are zero parameters, so baseline is 4. The description does not add parameter documentation (none needed). It effectively lists available response fields via features, which compensates somewhat.

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 the tool's purpose as 'Query the user's current crypto loan position with comprehensive details.' It lists specific metrics (LTV, total debt, collateral breakdown), which distinguishes it from related sibling tools like getCryptoLoanCommonAdjustmentHistory or getCryptoLoanCommonCollateralData.

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?

Use cases are explicitly listed (monitor LTV, view debt/collateral, track borrowing, etc.), providing context for when to use the tool. However, it does not explicitly exclude alternatives or mention when not to use it, leaving some ambiguity among the many sibling tools.

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