getCryptoLoanFixedSupplyOrderInfo

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

Only mentions rate limit (5 requests/UID). No disclosure of read-only nature, authentication needs, or error handling. Given no annotations, description should provide more behavioral context.

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?

Two sentences, front-loaded. However, it is under-specified for a 6-parameter tool; brevity does not compensate for missing essential information.

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, no parameter descriptions, and no annotations, the description is insufficient. Fails to explain return values, parameter dependencies, or use 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?

Six parameters (orderId, orderCurrency, state, term, limit, cursor) with 0% schema description coverage. Description adds no explanation of parameter usage, format, or constraints.

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?

States 'Query supply (lending) order details and history' with clear verb ('Query') and resource ('supply order details and history'). While distinct from siblings like getCryptoLoanFixedSupplyOrderQuote, it lacks explicit differentiation.

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 vs alternatives (e.g., getCryptoLoanFixedSupplyContractInfo). Does not specify prerequisites or context for use.

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