getCryptoLoanFixedSupplyContractInfo

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

The description discloses a rate limit of 5 requests per UID, which is a behavioral trait. However, with no annotations, it lacks details on authentication, error states, or what happens if no contracts are found. The rate limit is useful but not comprehensive.

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 very short (one line plus rate limit note), but it is under-specified rather than efficiently concise. It lacks structure and could include more detail without being verbose.

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 6 parameters, no output schema, and many sibling tools, the description is incomplete. It does not explain the return format, filtering options, or how it differs from similar tools like getCryptoLoanFixedSupplyOrderInfo.

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?

Schema description coverage is 0%, yet the description provides no information about the 6 parameters (orderId, supplyId, supplyCurrency, term, limit, cursor). It fails to add any meaning beyond the raw 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 clearly states it queries active supply contracts (lending positions), using a specific verb and resource. It distinguishes itself from related siblings like getCryptoLoanFixedSupplyOrderInfo and getCryptoLoanFixedSupplyOrderQuote, which are for order info and quotes, though not explicitly.

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?

No guidance on when to use this tool versus alternatives like getCryptoLoanFixedSupplyOrderInfo or getCryptoLoanFixedBorrowContractInfo. The sibling list includes many similar tools, but the description provides no context for selection.

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