vault_result

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

No annotations are provided, so the description carries the full burden. It discloses read-only behavior, which is worth something, but says nothing about authorization needs, what happens when a request is still pending or declined, or whether anything is mutated as a side effect.

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?

It is a single short sentence with no filler, which is fine structurally, but the brevity comes at the cost of clarity rather than from efficient information density.

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 lookup tool that takes an opaque id and has no output schema, the description should explain what the returned state looks like and how it relates to the prepare/begin-enrollment flow. Neither is present, leaving the agent unable to use the result meaningfully.

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?

There is one required parameter, request_id, with 0% schema description coverage, and the description says nothing about it. It does not explain where the 32-character request_id comes from (presumably prepare_request or vault_begin_enrollment) or what an invalid/stale id yields.

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 phrase 'Read enrollment state/reference only' gestures at a read of enrollment state but never says what is returned or what 'reference' means. It does not distinguish this from siblings like vault_status, vault_find, or get_operation_status, so an agent cannot tell what resource this actually resolves.

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 word 'only' hints at a read-only scope but there is no explicit when-to-use guidance, no prerequisites, and no naming of alternatives among the many vault_* and status siblings. Usage must be inferred entirely.

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