insLoanProductInfos

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful behavioral context: public access, guest permission, rate limit of 100 requests/s, and optional filtering semantics. This goes beyond the annotations without contradicting them.

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 compact and well-structured: a clear one-sentence purpose followed by concise bullet-point rules. Every line adds value, and the most important information is front-loaded.

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 simple public read-only endpoint with one optional parameter and no output schema, the description covers the necessary invocation details: purpose, filter behavior, access requirements, and rate limiting. Nothing essential is missing for an agent to select and call this tool correctly.

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?

Although schema description coverage is 0%, the description compensates by explaining that productId is an optional filter and that omitting it returns all products. This adds meaning beyond the raw schema, which only lists the parameter as a string.

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 function: 'Get institutional loan product information including leverage, risk lines, and trading pair whitelists.' It uses a specific verb and resource, and the listed fields help distinguish it from generic loan-related siblings. However, it does not explicitly differentiate itself from nearby tools like insLoanCoinDeltaAmount.

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?

The description provides clear operational context: it is a public endpoint allowing guest access, and productId is optional with defined behavior ('if omitted, returns all products'). It also mentions the rate limit. It does not explicitly direct the agent to alternatives or exclusion cases, but the usage context is clear enough for a simple read endpoint.

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