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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is partly covered. The description adds genuine value beyond that by enumerating the possible status outcomes and explicitly stating it is 'never authority to move money or proof of settlement', which tells the agent what the status does NOT grant.

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 sentences, front-loaded with the action and resource, then the status outcomes. Every clause carries information; the second sentence is dense but earns its length by enumerating states and limits.

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?

An output schema exists, so return-value explanation is not required, and the description still usefully previews the status enumeration. Combined with annotations it is nearly complete, with the only real gap being sibling disambiguation from get_capital_call_source_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, so the baseline is 3. The description reinforces that the job is tied to 'one exact document in your own X1 Vault', but adds no format or constraint detail beyond what the schema already states.

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 (capital-call job) scoped to one exact document in the user's X1 Vault, so intent is unambiguous. However, it never distinguishes itself from the very close sibling get_capital_call_source_state, leaving the agent to infer which state to fetch.

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 implied by the phrasing ('Read the existing capital-call job'), but there is no explicit when-to-use, no exclusions, and no routing to alternatives such as get_capital_call_source_state. The agent must infer selection from context alone.

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