get_otc_loan_product_info

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

With no annotations, the description must indicate behavioral traits. It only says 'Get', implying read-only, but gives no details on side effects, authorization, or rate limits. This is insufficient for an agent to understand the tool's behavior.

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 concise with two sentences, front-loading the purpose. It avoids unnecessary words, though it could benefit from a structured format like bullet points for parameters.

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 the lack of output schema, the description should explain what 'OTC loan product info' includes (e.g., rates, terms). It does not, and with many sibling tools, this omission hinders the agent's ability to choose 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?

The description explains the parameter 'product_id: Filter by product ID (optional),' adding meaning beyond the schema's name and type. However, it does not clarify what 'filter' means (e.g., returns one product or multiple) or the effect of an empty value.

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 states 'Get OTC loan product info,' which clearly identifies the action and resource. However, it does not differentiate from sibling tools like get_otc_loan_ltv or get_otc_loan_margin_coin_info, which also retrieve OTC loan data.

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 no guidance on when to use this tool versus alternatives. It does not mention context, prerequisites, or compare with other OTC loan info tools.

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