getRwaNavChart

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

No annotations provided, so description carries full burden. It discloses rate limit, authentication, and behavioral constraints (defaults, time span limit). Lacks mention of output format or pagination, but covers essential traits.

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 concise (3 sentences plus a note block). Front-loads purpose and then constraints. Could be slightly more structured but is efficient and clear.

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?

No output schema provided, and description does not explain return format or content of data points. Users cannot anticipate the response structure, making it incomplete for a data query tool.

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?

Schema coverage is 0%, so description must add meaning. It explains defaults and time span constraint for startTime/endTime, but productId is only described by name and type. Partially compensates, leaving productId ambiguous.

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?

Description clearly states it queries historical NAV data points for an RWA product. Verb 'Query' and resource 'historical NAV data points for an RWA product' are specific. Sibling tools like getMarketKline or getRwaProductList are distinct, so no confusion.

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?

Includes rate limit, authentication requirement (none), and constraints on time span (max 180 days) and default values for startTime/endTime. While it doesn't explicitly state when to use vs alternatives, the context implies it's for RWA NAV data.

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