vault_begin_enrollment

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that credential entry happens in the browser and that secrets must not be passed, but it omits lifecycle details such as whether the tool returns immediately, whether it opens a browser automatically, and how completion is retrieved.

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 two short, front-loaded sentences with no unnecessary wording. Both sentences carry relevant information: the browser-based entry action and the secret-handling constraint.

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 five-parameter enrollment tool with no annotations, no output schema, and no schema descriptions, the description is too sparse. It communicates the core browser-entry concept but leaves parameter meaning, return behavior, and follow-up flow undocumented.

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 0%, so the description needs to explain the five parameters. It mentions none of service, account, prompt, credential_type, or allowed_operations, and provides no meaning for the enum values beyond a general 'never pass secrets' warning.

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 states a specific verb and resource: request credential entry in the browser. It clearly indicates an enrollment-like interaction rather than retrieval, but it does not explicitly distinguish this tool from siblings such as vault_export_credential or vault_result.

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 phrase 'Request credential entry in the browser' implies when to use the tool, and 'Never pass secrets' gives an important usage constraint. However, it does not state when to use alternatives such as vault_result or vault_decline, nor does it define prerequisites or exclusions.

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