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

Annotations already declare readOnlyHint=true and non-destructive, so safety is covered. The description adds meaningful beyond-annotation context: values are masked and secrets are never returned, which tells the agent what it will and won't see. It doesn't discuss pagination or limits, but the masking disclosure is a substantive behavioral trait not captured by annotations.

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?

Front-loads the core action and the masking caveat, then closes with the sibling distinction. Each sentence earns its place, though the quoted example question is slightly verbose and could be trimmed without losing meaning.

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 single-parameter read-only listing tool with full schema coverage, annotations, and an output schema present, the description covers what it returns, what it masks, and how it differs from the global-integrations sibling. Nothing an agent needs to call it correctly is missing.

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% and there is a single required integer project_id with its own description. The description doesn't add syntax or meaning beyond 'a project's environment variables', which is expected given the schema already documents the parameter fully. Baseline 3 applies.

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?

States a specific verb (List) and resource (project environment variables) and enumerates the returned fields (name, title, description, docs URL, category). It explicitly distinguishes itself from the sibling dreamagent_list_global_integrations, so an agent can route correctly without opening either schema.

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?

Gives concrete when-to-use conditions: 'to see which integrations a project already has before adding more, or to answer "what keys does my project have?"'. It also names the alternative (global integrations) and the distinction between project-specific vars and global ones, so the selection decision is unambiguous.

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