getRwaProductList

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

Description mentions rate limit (20 req/s IP) and lack of authentication, which affects the userQuota field. However, it does not state whether the tool is read-only or describe error handling or return format, leaving gaps despite no annotations to cover.

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?

Description is very concise (two sentences plus rate limit) with no fluff. Purpose is front-loaded, and every sentence adds value.

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?

While the tool is simple, the description lacks information on parameter usage, response structure, and potential pagination. Given one optional parameter and no output schema, more context is needed for effective use.

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 sole parameter 'coin' has no schema description and the tool description does not explain its purpose. With 0% schema coverage, the description fails to add meaning; it is unclear if it filters products or is required.

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 queries a list of RWA products and enumerates specific metadata fields (APR, NAV, stake limits, precision), distinguishing it from sibling tools like getRwaOrderList or getRwaPositionList.

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. The description only lists behavioral info (rate limit, authentication) but does not specify use cases or exclusions.

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