update_repo_visibility

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It indicates a mutation ('update', 'make private or public') but does not disclose side effects, permission requirements, reversibility, or any consequences of changing visibility. For a mutating operation, this is a notable transparency gap.

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?

A single precise sentence with no filler. The core action, resource, and outcome are stated upfront, earning its place and avoiding redundant restatement of the parameter names.

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?

With only two simple required parameters and an output schema present, the description is almost sufficient. Nevertheless, no context is given about required permissions, side effects, or behavior on unauthorized operations. For a mutating tool without annotations, this small gap prevents full confidence.

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 has 0% description coverage, but the description maps 'private/public' to the 'private' boolean parameter, clarifying that true privately identifies the private state and false means public. However, it does not clarify the expected format of the 'repo' parameter (e.g., owner/repo), relying heavily on the parameter name. The description compensates minimally for the schema gap.

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 a specific action ('Update'), identifies the resource ('repository privacy/visibility settings'), and clarifies the exact outcome ('make it private or public'). It is distinct from the sibling read-only tools, so an agent can tell this tool's purpose immediately.

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 implies when to use the tool: whenever a repository's visibility needs changing between private and public. However, it does not explicitly discuss when not to use it, mention alternatives, or state prerequisites such as required permissions or repository ownership, leaving usage context mostly implicit.

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