Set course visibility (admin)

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

The description adds meaningful behavioral context beyond the annotations: making a course public exposes it to every Repovive user, confirming before calling is advised, and site administration rights are required. This is exactly the kind of impactful side-effect disclosure an agent needs before invoking an admin visibility mutation.

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?

Three concise sentences front-load the core action and impact, then deliver the caution and permission requirement. Every sentence earns its place with no redundancy or filler.

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 two-parameter, idempotent admin mutation with a full input schema and an output schema present, the description covers action, platform-wide impact, confirmation guidance, and required permissions. Nothing essential is missing.

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 description coverage is 100%, so the schema already documents both parameters. The description reinforces the meaning of is_public by discussing public vs. unpublish, but it does not add parameter-level detail beyond what the schema provides.

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 uses a specific verb and resource: 'Publish or unpublish a course platform-wide.' It clearly distinguishes this visibility-setting operation from the many sibling course tools by emphasizing platform-wide scope and admin rights.

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 gives clear context for when to use the tool: to publish or unpublish a course platform-wide. It also provides important usage cautions ('confirm before calling') and a prerequisite ('Requires site administration rights'), though it does not explicitly contrast it with any alternative sibling tool.

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