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

Annotations already declare it as a read-only, idempotent, non-destructive, closed-world call, and the description adds real behavioral context on top: it returns either complete proof-backed facts or a typed hold, and explicitly disclaims confirmation, obligation creation, write authorization, money movement, and settlement verification. That is substantive disclosure beyond the annotation set.

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 front-loaded sentences with no filler, and the core action leads. The second sentence is a dense negative clause list that is slightly jargon-heavy ('strict source-state projection', 'typed hold'), but every clause carries scope information.

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?

With an output schema present, the description need not detail return shape, and it still conveys the semantic return contract (facts vs. typed hold) and the capability boundaries. The only gap is the absence of guidance on when to choose this tool over sibling lookups such as get_capital_call_job_state.

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% for the single documentId parameter, and the description adds no format or sourcing detail beyond what the schema already says. Baseline 3 is appropriate when the schema does the work.

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 ('Read') and resource ('one capital-call notice from your own X1 Vault') and frames the scope ('strict source-state projection'). It implicitly separates itself from the similarly named sibling get_capital_call_job_state, but the distinction is left to be inferred rather than stated.

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 explicit when-to-use guidance or named alternative; the agent must infer usage from the name and the pipeline hint in the schema ('documentId returned by get_vault_documents'). The negative list (never confirmation, obligation, write, coordination, money movement, settlement) clarifies scope boundaries, which is useful, but those are exclusions rather than usage directions.

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