doppler_secrets_set

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 does not state side effects (overwrites existing secrets?), auth requirements, environment interplay (which config does it target?), or reversibility. For a mutation tool with zero annotations, this is a significant gap.

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?

Single concise sentence with no waste. However, at only 7 words, it borders on under-specification rather than conciseness, though for a simple tool it's acceptable.

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 mutation tool with no annotations and no output schema, the description is thin. It does not explain overwrite behavior, config targeting defaults, post-set verification options, or prerequisites. The 4-parameter schema is fully covered but the tool's operational context is largely unexplained.

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%, so the schema already documents all 4 parameters. The description adds nothing beyond the schema—it doesn't clarify optionality nuances (e.g., what happens if config/project are omitted), value format, or interaction between parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Set a secret value in Doppler' uses a specific verb (Set) + resource (secret value in Doppler). It clearly distinguishes from siblings like doppler_secrets_get/list/delete, though it doesn't explicitly contrast them.

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 provides no guidance on when to use this tool versus the alternatives. It doesn't mention prerequisites like doppler setup, whether config/project are required, or any caveats about which config the secret applies to. Some context is implied (it's the write counterpart to get/list), but no explicit guidance is given.

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