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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real epistemic context: source-linked deadlines, labeled opinions, coverage reporting for disabled/stale sources, and no guessing of unlinked parties. However it says nothing about pagination, default date window, or result volume behavior for a 15-param listing tool.

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 dense sentences with no filler, but they are front-loaded with output-quality claims rather than the primary action, so the agent reads provenance details before learning what the tool does. Content is efficient but misordered for selection.

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?

A 15-parameter, zero-coverage, no-output-schema tool needs the description to explain both query dimensions and return shape. The description covers trustworthiness of results well but leaves the entire parameter surface and pagination model undocumented, which is a significant gap for correct invocation.

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 0% across 15 parameters, so the description must compensate and largely fails. Terms like 'dated deadlines', 'ticker-resolution confidence', 'coverage reports disabled or stale sources' hint obliquely at dateField, symbol, and source, but from/to semantics, upcoming vs changed, status, agency, sector, limit and offset are entirely unexplained.

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 enumerates the content domain (regulatory, clinical, legal, sanctions, trade events worldwide) but never states a verb or that it returns a queryable calendar listing, leaving 'Get catalyst calendar' to carry that load. It does not distinguish this from siblings like catalysts.event, catalysts.changes, or macro.calendar.

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?

There is no statement of when to call this versus catalysts.changes (revision feed), catalysts.event (single event detail), or macro.calendar. The presence of from/to params implies a date-windowed listing, but nothing tells the agent defaults, required-ness, or the retrieval mode.

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