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

The description transparently discloses that secret values are ALWAYS masked and that MCP has no path to decrypted secrets. This is consistent with the readOnlyHint annotation and adds important behavioral detail beyond the annotation.

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 concise and well-structured, with no redundant or filler content. It conveys the purpose, output format, masking behavior, and appropriate use cases in just two sentences.

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?

Despite having no output schema, the description tells the user what kind of output to expect (.env or JSON text), that secrets will be masked, and how the output can be used. This is sufficient context for a simple export operation.

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?

All three parameters are fully described in the input schema, including format, environmentId, and projectId semantics. The tool description adds no additional parameter-level meaning, so it stays at the baseline for high schema coverage.

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 specific action and resource: 'Export an environment's variables as .env or JSON text.' It clearly identifies the output format and the target object, making the tool's purpose unambiguous.

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 gives explicit usage guidance: output is suitable for review and for feeding into import_variables, and it directs users to the web app when they need real, unmasked secret values. This provides clear conditions for when to use this tool versus an alternative source.

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