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

Annotations already establish that this is a read-only, closed-world operation. The description adds useful context beyond that: the data is 'Free' and 'source-backed,' unknown fund identity/investor access/liquidity remain explicit, and the tool does not provide live quotes or execution. It does not, however, describe return shape, pagination, or how version selection affects behavior, so it adds moderate rather than rich context.

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 four sentences are compact and each carries some meaning—scope, disambiguation, explicit unknowns, exclusions—but they are front-loaded with abstraction ('Free source-backed documentation of Treasury distribution and asset-settlement protocols') rather than an actionable statement of what the tool returns. The dense jargon makes the definition harder to parse than its length suggests.

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?

This is a zero-required-parameter read tool with 100% schema coverage and no output schema, so the description need not document every field. Still, it does not connect the parameters to behavior—e.g., what version 2 returns when no selection is supplied—and its abstract phrasing leaves an agent uncertain what the 'documentation' actually contains. Adequate but with clear gaps.

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%, so the schema fully documents ticker, version, and record_id, including the enum for version and the version-2 only note on ticker. The description adds no parameter-level meaning—such as how record_id selection interacts with ticker—so the 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?

The description conveys a high-level purpose—source-backed documentation of Treasury distribution and settlement protocols—but never states a concrete verb-plus-resource like 'returns access evidence for a ticker.' Its abstract disambiguation language ('announced access path' vs 'identified fund') hints at scope without letting an agent tell it apart from siblings such as get_rwa_instrument or get_rwa_history.

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?

The only usage guidance is negative scope—'No live quote, execution or eligibility determination'—which implies when not to use it. There is no positive statement of when to choose this over the twelve sibling tools, no mention of prerequisites, and no alternative named for live quotes or eligibility checks.

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