getAdvanceEarnProductExtraInfo

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

Despite no annotations being provided, the description discloses important behavioral traits: quotes are sourced from institutional market makers, update frequently at the second level, are real-time, and require no authentication. It also notes rate limits, giving the agent sufficient context for safe usage.

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 four sentences, front-loading the main purpose. It efficiently includes the purpose, data source, update frequency, rate limit, and a usage tip without redundant 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 the absence of an output schema, the description provides adequate context by mentioning the return includes target prices and APY. The rate limit and WebSocket alternative are also helpful. However, more detail on the exact structure of the quote data could improve completeness.

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 does not elaborate on the parameters beyond the schema. With schema description coverage at 0%, the description should compensate, but it only mentions 'specific Dual Assets product', while the category enum includes other product types. This could cause confusion about which categories are valid for this tool.

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 that the tool gets real-time quotes (target prices and APY) for a specific Dual Assets product. This distinguishes it from sibling tools like getAdvanceEarnProduct, which retrieves product details rather than quotes.

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 explicitly mentions that no authentication is required, provides a rate limit of 50 req/s per IP, and advises using WebSocket for real-time updates while using this endpoint for initial load or fallback. This gives clear guidance on when and how to use the tool versus alternatives.

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