github_orgs_get_immutable_releases_settings_repositories

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

No annotations provided and description only states the basic function. Missing information on whether it is read-only, required permissions, pagination behavior (though schema mentions pagination), or any side effects. The description carries full burden but provides minimal behavioral context.

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?

Single sentence is concise with no wasted words. However, it could be slightly more informative without being verbose. Structure is front-loaded and clear.

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?

For a simple listing tool with no output schema and no behavioral details, the description is incomplete. It lacks information about the return format (e.g., list of repository names/IDs), error handling, and any prerequisites. Missing context beyond the bare action.

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?

Schema coverage is 100% with descriptions for all 3 parameters. The description does not add extra meaning beyond the schema, but the baseline is 3 due to high coverage. The description could clarify what 'selected repositories' means but is adequate.

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?

Description clearly states the action 'List' and resource 'selected repositories for immutable releases enforcement'. It is specific and distinguishes from sibling tools like get_immutable_releases_settings which retrieves settings, not repositories.

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 on when to use this tool versus alternatives like set_immutable_releases_settings_repositories or enable/disable variants. The description provides no context for usage.

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