github_actions_list_environment_variables

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

Without annotations, the description should disclose behavioral traits such as being a read-only operation or supporting pagination (the schema includes per_page and page). The description does not mention these, leaving the agent unaware of pagination behavior and the non-destructive nature.

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 short at three words, which is under-specified rather than concise. While it avoids verbosity, it lacks structure and fails to include essential context, making it less helpful than a slightly longer but more informative description.

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 the complexity (5 parameters, no output schema, many siblings), the description is incomplete. It does not explain the return format, pagination, or how to differentiate from similar tools. More detail is needed for an agent to use it effectively.

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 coverage is 100%, so the description adds no additional meaning beyond the parameter names and types. The baseline is 3, and since the description does not enrich the understanding of parameters (e.g., clarifying that environment_name refers to the specific environment), the score remains 3.

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 'List environment variables' clearly states the verb and resource, distinguishing it from sibling tools that get a single variable or list secrets. However, it omits the scope (per environment, as indicated by the required environment_name parameter in the schema). This minor lack of specificity prevents a 5.

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 like github_actions_get_environment_variable or github_actions_list_environment_secrets. The description lacks context for proper selection among the many sibling tools.

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