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

The readOnlyHint annotation already indicates no mutation, and the description adds meaningful behavioral detail by stating that secret values are always masked. It also mentions the organization context prerequisite. This goes beyond the annotation without contradicting it.

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 brief and well-structured, with three concise sentences that cover purpose, behavior, usage direction, and context requirement. No unnecessary information is included.

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?

The description is complete for a simple read operation: it explains what is returned (resolved variables), important behavior (masking), and usage context. Since there is no output schema, the description could ideally mention the exact return format, but the current level of detail is sufficient for most callers.

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 already provides full descriptions for both parameters, including the optionality of projectId and the required environmentId. The description does not add additional semantic detail beyond the schema, so a baseline score 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 clearly states the tool retrieves resolved variables for a specific environment and explicitly mentions that secret values are masked. The verb 'get' and resource 'environment variables' are specific, and the description helps distinguish it from related tools that export or resolve 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?

The description gives direct usage guidance: use this to read resolved values, and use set_environment_variables to change them. It also notes the requirement for organization context. However, it does not contrast with sibling tools like resolve_variables or export_variables, which could further clarify when this specific read tool is preferred.

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