vault_inject_env

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

With no annotations, the description carries the full behavioral burden. It does earn credit for two non-obvious disclosures: handles are resolved into the environment (rather than the command receiving raw secrets directly), and output is "scrubbed" before return. It says nothing about the fact that this executes an arbitrary subprocess, whether it requires approval, what privileges it runs with, or whether the command is silently mutated.

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?

A single front-loaded sentence with no filler, and the resolution mechanic leads ahead of the return behavior. It is dense rather than padded, though the run-on construction packs three distinct facts together without separation.

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 subprocess-executing tool with no annotations, no output schema, 0% parameter coverage, and a nested object parameter, this is too thin. The agent learns the core mechanic but not the side-effect profile, permission requirements, or what any of the four parameters actually accept.

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% across four parameters, so the schema documents nothing and the description must compensate. The description only loosely implies that "env" holds the handles to resolve; it says nothing about command, args, cwd, or the fact that env is a nested string-to-string object. The nested-object structure is entirely unexplained.

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 names a specific verb ("Resolve"), its input ("opaque secret or lease handles"), its effect ("into a subprocess execution environment"), and its output ("scrubbed command output"). That is far more specific than a name restatement, but it never differentiates itself from the sibling vault_run_command, which an agent would plausibly confuse with this.

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 statement of when to use this tool rather than vault_run_command, vault_get_secret, or vault_lease_secret, and no mention of prerequisites or exclusions. The use case is only inferable from the mechanic described, which leaves routing between siblings to guesswork.

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