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

Adds rich context far beyond the read-only/idempotent annotations: data is pulled daily from Fed/BLS/BEA pages and never hand-entered, records verified more than 35 days ago return 503 and are never charged, and DST-aware conversion is documented. Freshness and billing failure behavior are exactly the non-obvious traits an agent needs.

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?

Front-loaded with the resource and its contents, then behavior and cost. Efficient overall, though the first sentence is dense and the pricing/solana-chain detail could be trimmed without losing call-relevant meaning.

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?

An output schema exists, so return shape needn't be described; the description instead covers the things schema cannot: data provenance, freshness cutoff, failure semantics, and payment cost. Complete for a monetized external-data 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 100%, so the schema already documents 'days' (range/default) and 'type'. The description names the event categories (FOMC, CPI, NFP, PCE) matching the type parameter but adds no syntax, format, or interaction detail beyond the schema. Baseline 3 applies.

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?

States a specific resource (FOMC, CPI, NFP, PCE calendar) with the exact contents: next Fed rate decisions, release dates, UTC times converted from NY time, source URLs, and verification timestamps. No sibling tool competes with a macro-event calendar, so no differentiation is needed. An agent immediately knows what it returns.

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?

'For traders' gives an implicit audience but there is no explicit when-to-use, when-not-to-use, or named alternative. With no competing sibling, the gap is smaller, but the description still leaves usage conditions to inference.

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