vault_entry_inject_env

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

No annotations provided, so description must carry burden. Clearly discloses that the secret is decrypted server-side and written directly, and that plaintext is never returned to the agent – critical security behavior.

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 highly informative sentences. Front-loaded with action. Zero waste – every sentence adds value (purpose, security behavior, usage advice).

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?

Given 4 required parameters, no output schema, and simple write operation, the description fully covers purpose, behavior, security, and usage guidance. No gaps for an AI agent to correctly invoke.

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%, baseline 3. Description adds no additional meaning beyond what schema already provides for each parameter. It gives overall context but no per-parameter enrichment.

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?

Clearly states 'Write a vault secret directly into an environment variable file (.env)' – specific verb+resource+target. Explicitly distinguishes from sibling tool 'vault_exec' with 'Use this instead of exec file-writing commands.'

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?

Provides explicit guidance on when to use this tool ('Use this instead of exec file-writing commands') and describes a key behavior (plaintext never returned). No ambiguity about context.

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