github_actions_get_org_variable

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

With no annotations, the description should disclose behavioral traits like idempotency, authentication requirements, or side effects. The current description is limited to a terse action statement and fails to provide any behavioral context beyond the base meaning.

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 highly concise with a single sentence that directly states the purpose. While minimal, it avoids unnecessary words. However, the brevity slightly limits completeness, preventing a top score.

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 insufficient for an agent to fully understand the tool's capabilities. It does not explain return values, constraints, or how it compares to siblings. Given the simple nature of the tool, more context is needed to ensure correct usage without guessing.

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 parameter descriptions, but they are trivial ('org', 'name'). The tool description adds no additional context about the parameters, such as expected formats or relationships. Given the high schema coverage, the baseline of 3 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 an organization variable' clearly states the action (get) and the resource (organization variable). However, it does not differentiate from siblings like 'github_actions_get_org_secret' or 'github_actions_get_env_variable', missing an opportunity to clarify that this retrieves an Actions variable specifically.

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 or create tools. The agent must infer usage from the tool name alone, which is insufficient for effective selection among many similar siblings.

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