github_orgs_set_immutable_releases_settings

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

Without annotations, the description must carry the burden of behavioral disclosure. 'Set' implies mutation, but there is no mention of permission requirements, irreversible changes, or side effects. The agent learns nothing beyond the trivial fact that it modifies settings.

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, achieving conciseness, but it lacks structure or additional details. It is not well-organized for scanning and omits critical context, making it less useful despite its brevity.

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 of the domain (many sibling tools for immutable releases), the description is severely incomplete. It does not explain what immutable releases settings are, what the request body should contain, or how this tool differs from related tools. No output schema is provided, leaving the agent uninformed about return values.

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 description adds no information about parameters. The input schema documents `org` and `body`, but the description does not explain what the `body` object should contain (e.g., expected fields, structure). With 100% schema coverage, the baseline is 3, but the description fails to add value beyond the schema, and the schema's `body` description is generic.

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 states the verb 'Set' and resource 'immutable releases settings for an organization', making the basic purpose clear. However, it does not distinguish from sibling tools like `github_orgs_set_immutable_releases_settings_repositories`, which sets per-repo settings, nor does it specify what 'settings' includes.

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_orgs_get_immutable_releases_settings` or `github_repos_enable_immutable_releases`. An AI agent receives no context for tool selection.

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