github_actions_get_hosted_runner_for_org

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

No annotations are provided, so the description carries the full burden. However, it does not disclose any behavioral traits such as required permissions, rate limits, or what the response contains. For a read operation, minimal context is given.

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 a single, short sentence that is concise and free of fluff. However, it could be structured to include more details without losing conciseness, such as specifying the output format.

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 the complexity of the GitHub Actions API, the description lacks important context like what data is returned, required permissions, or how to obtain the runner ID. It is incomplete for an AI agent to reliably invoke the tool without additional knowledge.

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, but those descriptions are just the parameter names ('org', 'hosted_runner_id') and add no additional meaning. The description does not provide extra context for the parameters, so it neither improves nor degrades the understanding beyond the schema.

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 verb 'Get' and the resource 'GitHub-hosted runner for an organization', distinguishing it from sibling tools like github_actions_list_hosted_runners_for_org (list) and github_actions_create_hosted_runner_for_org (create). However, it does not explicitly mention the unique identifier (hosted_runner_id) required to fetch a specific runner.

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 vs alternatives (e.g., listing vs getting a specific runner). It does not mention prerequisites, such as needing the runner ID from a list operation, or any exclusions.

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