github_actions_set_self_hosted_runners_permissions_organization

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Set' implying mutation, but does not describe whether settings are overwritten, merged, or what permissions are required. The effects on the organization's self-hosted runners configuration are unclear.

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 sentence, which is concise, but its vagueness means it fails to convey sufficient information. Every word should add value; here, 'settings' is too generic.

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 (mutation tool, no output schema, no annotations), the description is incomplete. It does not mention return values, side effects, or required permissions. For a tool that modifies organization settings, more context is needed.

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 schema covers both parameters, but the descriptions are minimal ('org' is just 'org', 'body' is 'Request body (JSON object)'). The tool description adds no further meaning, so an agent cannot infer valid fields for the body object. Baseline 3 is lowered due to low-quality schema descriptions.

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 'Set self-hosted runners settings for an organization' identifies the resource and action, but 'settings' is vague and does not specify what aspects of self-hosted runner permissions are being set. Among many sibling tools, this does not clearly differentiate from other setter tools like 'github_actions_set_selected_repositories_self_hosted_runners_organization'.

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, nor any prerequisites or context. The description lacks any indication of typical use cases or when not to use this tool.

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