getRwaNavChart

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

Annotations already mark readOnlyHint=true, and the description adds useful behavioral context beyond that: a 20 req/s IP rate limit, no authentication requirement, default startTime/endTime behavior, and a 180-day time-span cap. This is strong added transparency, though it doesn't describe return/error 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 purpose is front-loaded and every subsequent line (rate limit, auth, defaults, max span) adds operational value. No redundant filler.

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 read-only query, the description gives enough to call it correctly with only productId plus defaults, and it covers auth, rate limits, and range constraints. Minor gaps are unstated time units and no output schema, but the tool's purpose makes return values reasonably predictable.

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 the description must carry parameter meaning. It does explain startTime/endTime defaults and the 180-day span constraint, but it leaves productId semantics implicit and doesn't state the time format/units, so compensation is partial.

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 opens with 'Query historical NAV (Net Asset Value) data points for an RWA product,' which clearly identifies the verb, resource, and data scope. It doesn't name a sibling alternative, but the resource/verb combination is distinctive enough among the RWA family to avoid 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?

The intended use is implied by the purpose statement: fetch historical NAV chart data for an RWA product. There is no explicit when-to-use guidance or mention of alternatives, so it earns the implied-usage score rather than a higher explicit-routing score.

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