doppler_projects_list

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. However, 'list' is inherently a read-only operation, which is reasonably transparent. The description doesn't clarify whether results are paginated, ordered, or what the response format looks like, but for a simple list operation this is acceptable.

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 concise sentence that fully captures the tool's purpose with zero waste. Highly front-loaded and efficient.

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 zero-parameter, simple read/list tool with a clear name and no output schema or nested objects, the description is adequately complete. The complexity is low enough that the minimal description suffices. It may not state return format, but for a simple list operation this is a minor gap.

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?

The schema has zero parameters and schema coverage is 100%, meaning everything about parameters is already fully specified by the absence of parameters. The description adds nothing about parameters, but there are none to document, so the baseline of 4 is appropriate.

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 uses a clear verb+resource pattern ('List all Doppler projects'). It clearly states the operation (list) and resource (projects). However, it doesn't distinguish from sibling tools that list other resources (configs, environments, secrets) — though the resource names differ and are fairly self-evident from the tool names.

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 when to use it (when you need a listing of projects), but provides no explicit guidance on when NOT to use it or which alternative tools might fit better. No filtering, pagination, or context hints are mentioned. It's minimally adequate but lacks explicit alternative/exclusion guidance.

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