doppler_run

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description fails to mention that secrets are exposed to the subprocess as environment variables (a security-relevant behavior), how the exit code propagates, whether it streams output, or what happens if secrets/credentials are missing. For a command-execution tool with zero annotation coverage, more behavioral context is expected.

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 a single clear sentence with zero waste. It is appropriately sized and front-loaded. It could arguably add a bit more behavioral detail, but as written it is efficient and to the point.

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?

A tool that executes arbitrary commands with injected secrets is high-stakes, yet the description provides minimal context. Given no output schema and no annotations, the description should carry more weight: it doesn't explain what happens on successful/failed runs, exit code semantics, whether output is streamed, key format conventions for env vars, or fallback behavior. This is under-specified for a command execution tool.

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 coverage is 100%, so the schema already documents all three parameters. The description adds no additional parameter-level meaning beyond what the schema provides. The command parameter description and config/project descriptions in the schema already cover the semantics, so the description adds little value here.

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 clear verb+resource ('Run a command with Doppler secrets injected as environment variables'). It clearly differentiates this from sibling tools: the secrets_* tools get/list/set/delete secrets, while doppler_run actually executes a command with those secrets as env vars. This is distinct from the rest of the tool family.

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 description implies it is used when you want to execute a command with secrets available as environment variables, which distinguishes it from the secrets management tools. However, it does not explicitly state when not to use it, nor mention the dependency on project/config being setup (implied via 'optional if set via doppler setup'), nor alternative non-Doppler approaches.

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