Get Environment Variables

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

The readOnlyHint annotation already establishes the safe read-only nature, and the description adds valuable behavioral details: variables are resolved, secret values are always masked, and organization context is required. This goes beyond the structured annotations, though it does not disclose permissions or failure behavior.

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?

Two short sentences deliver the core operation, a security-relevant behavior, and a context requirement with no filler. The most important information is front-loaded.

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 two-parameter read-only tool, the description covers the operation, masking behavior, and the organization context requirement, while the schema handles parameter semantics. The lack of an output schema leaves minor ambiguity about the return structure, but the description is largely complete for this simple use case.

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 projectId and environmentId are already well documented in the input schema. The description only reinforces the idea of a specific environment and resolved values without adding any new parameter-level detail.

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 clearly identifies the operation ('Get'), the resource ('resolved variables'), and the target scope ('a specific environment'). It also adds useful security behavior about masking, but it does not explicitly differentiate this tool from related sibling tools like resolve_variables or export_variables.

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 is provided on when to use this tool versus alternatives such as resolve_variables, list_personal_variables, or get_environment_auth. The only stated condition, 'Requires organization context,' is a prerequisite rather than a usage rule, so an agent gets little help selecting between similar tools.

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