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

Beyond the readOnly/idempotent annotations, the description discloses the credit cost, the default time zone (London), and that times are returned in Eastern, UTC and local. It does not mention caching or how far ahead the schedule extends, but the added operational context is solid for a read-only lookup.

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 lead question front-loads the task and the detail follows in a logical order. The audience sentence ('For traders, economists and Fed watchers') and the cost note are filler-adjacent, but overall the text is tight for the amount of context delivered.

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 one-optional-parameter, read-only schedule lookup with no output schema, the description covers what is returned (the covered month and times in three zones), the time-zone behavior, the cost, and the scope limit. An agent has everything needed to call it and interpret the result.

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 description coverage is 100% and the single optional parameter is fully documented in the schema (IANA zone, default Europe/London). The description's '(London by default)' merely restates the schema, so 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 verb and resource ('next scheduled Personal Income and Outlays release') and explicitly says which inflation measure it carries (PCE and core PCE), which is enough to separate it from the CPI, PPI and jobs-release siblings without naming them.

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?

Gives a clear scope boundary — 'It gives the schedule only, not the inflation figures' — which tells an agent when not to use it. It never names an alternative (e.g. next_cpi_release or bea_release_dates_for_year) for related needs, so it falls short of full when-to-use/when-not routing.

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