github_actions_get_environment_variable

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

Without annotations, the description carries full burden. It fails to disclose authentication needs, rate limits, return format, or error behavior (e.g., if variable does not exist). It only says 'Get' without specifying what is returned (name, value, etc.). Minimal disclosure.

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 extremely concise (one sentence) but lacks structure such as bullet points, examples, or sections. It is not verbose, but it is under-specified at only 4 words. Adequate but could be improved.

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?

Given no output schema and minimal annotations, the description is incomplete. It does not explain return values, prerequisites (e.g., environment must exist), or behavior on error. Essential context for a simple get operation 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 descriptions are just parameter names (e.g., 'owner', 'repo'), offering no additional meaning. The tool description does not elaborate on their purpose or relationships. With 100% schema coverage but unhelpful descriptions, the baseline for high coverage is 3, but the description adds no value, warranting a 2.

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 'Get an environment variable' states the verb and resource but is a tautology of the tool name. It does not specify that it retrieves a variable from a specific GitHub Actions environment in a repo, nor does it differentiate from sibling tools like get_environment_secret or list_environment_variables. The purpose is clear but minimal.

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 list_environment_variables, get_environment_secret, or create_environment_variable. The description lacks any context about prerequisites or scenarios.

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