github_actions_get_repo_variable

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

No annotations are provided. The description 'Get a repository variable' implies a read-only operation but does not explicitly state it, nor does it disclose any behavioral traits such as return format, pagination, permissions, or side effects. It adds no value beyond the tool name.

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 very concise at 4 words, front-loading the purpose. However, it is so brief that it omits useful context. It is not verbose, but it could be slightly more informative without losing conciseness.

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 simple nature of the tool and the lack of output schema or annotations, the description should at least indicate what is returned (e.g., 'Returns the variable value and metadata'). It fails to provide this, making it incomplete for an agent to understand the full context.

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 input schema has 100% coverage with descriptions that are merely the parameter names (owner, repo, name), which are trivial. The tool description does not add any additional semantics. Baseline for high coverage is 3, so this 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 'Get a repository variable' clearly states the action (get) and the resource (repository variable). However, it does not differentiate from siblings like github_actions_get_org_variable or github_actions_get_repo_secret, as it fails to specify that it retrieves a variable (as opposed to a secret) and that it operates at the repository level.

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 provides no guidance on when to use this tool versus alternatives. It does not mention when to use this over github_actions_get_repo_secret or github_actions_list_repo_variables, leaving the agent to infer usage from the name alone.

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