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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), yet the description adds substantial behavioral context: it defines actionType semantics (NEWT/CORR/EROR/MODI/TERM) and, critically, discloses that corrections and cancellations arrive as NEW records rather than edits, making this an append-only event log, not a snapshot. This is exactly the kind of non-obvious trait 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?

The description is long but front-loaded and information-dense: purpose and source come first, then coverage, then record fields and actionType semantics. Every clause carries weight (the append-only caveat is essential), though the regulator/asset-class enumeration is somewhat verbose relative to what the schema already provides.

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 filtered query tool this is complete: source, freshness ('live'), coverage, record contents, and the append-only correction semantics are all described, so an agent understands both what it returns and how to interpret actionType. No output schema is needed given the inline description of record fields.

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 both enums (regulator, asset_class) are fully documented with their value meanings in the schema. The description largely reiterates those enum meanings rather than adding syntax or constraints beyond them, so the baseline 3 for a schema-documented parameter set is appropriate.

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 + resource (most-recently disseminated swap transactions) and pins down the exact source (DTCC pddata.dtcc.com, CFTC Part 43). It also scopes the data by regulator (CFTC/SEC/CA) and asset class, and the 'live / most-recently' framing implicitly separates it from the bulk dtcc_swaps_dissemination_files sibling.

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?

Usage is only implied: 'most-recently disseminated... live' suggests this is for current/recent trade activity, and it implicitly contrasts with the file-based sibling. But it never names an alternative or states when to use this versus dtcc_swaps_dissemination_files, so the routing decision is left to inference.

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