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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds meaningful context beyond that: cache-only operation, source clocks, and the limitation that no executable prices or regulatory eligibility determination are provided. It does not cover auth or rate limits, but those are less central here.

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?

Two sentences are front-loaded with purpose and then bounded by constraints. Every clause contributes needed scope or limitation, with no filler or repetition.

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?

With no input parameters, an output schema present, and rich annotations, the description supplies enough context to select and invoke the tool correctly. It clarifies the research-only, cache-only nature and data domains, though it could be slightly more explicit about how the source clocks affect 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 tool has zero input parameters, so there are no parameter semantics to clarify. Per the scoring baseline for a parameterless tool, a 4 is appropriate; the description adds no contradictory or misleading parameter information.

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 uses a specific verb ('Read') and enumerates distinct resources: dated USD/INR funding, ECB/CBUAE VAT FX references, and CFTC COMEX gold positioning. The GIFT City and India–UAE framing plus the cache-only research limitation distinguishes it from broader siblings like funding_stress_now or world_markets_context.

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?

It states a clear context ('Cache-only research with source clocks') and an exclusion ('no executable prices or regulatory eligibility determination'), telling the agent when this tool is appropriate. However, it does not name a sibling alternative to use instead when executable or regulatory data is needed, which keeps it from a 5.

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