doppler_secrets_get

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

No annotations are provided, so the description carries full burden of behavioral disclosure. It doesn't state whether config/project are required when doppler setup hasn't been run, what happens for missing secrets (error vs empty), or whether the value is sensitive/redacted. This is a secrecy-sensitive read tool with zero behavioral detail.

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 sentence, no wasted words. It's appropriately brief and front-loaded, but arguably under-specified rather than concisely complete. Not verbose, but also conveys almost nothing beyond the name.

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 security-sensitive read tool with no output schema and no annotations, the description is incomplete. It doesn't explain return value format, behavior with missing config/project, permission requirements, or error cases. Sibling tools (set/delete) and the secrets-domain context demand more behavioral detail.

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 baseline is 3. However, the description adds nothing beyond the schema. The schema documents name/config/project but the description provides no additional context about how project/config interplay works (e.g., when you must supply them vs rely on setup), nor clarifies the required parameter. Slight deduction for adding zero value.

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 'Get a secret value from Doppler' uses a clear verb (get) and resource (secret value). It distinguishes the read operation from siblings like doppler_secrets_set and doppler_secrets_delete, though it doesn't explicitly name them or contrast. Basic purpose is clear but minimal.

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?

No guidance on when to use this vs alternatives, no prerequisites mentioned, and the schema hints at optional project/config but no clarity on when setup is needed. The description gives no usage context or exclusions. An agent has to infer from the schema what context is required.

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