copr_enable_repository

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

Since no annotations are provided, the description carries full burden. It discloses that the tool provides instructions rather than performing the action directly, and that root privileges are required. This is valuable behavioral context beyond the input schema.

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 consists of two short, direct sentences. The first sentence states the primary action, and the second adds important context. It is concise without unnecessary words.

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 no annotations and 0% parameter coverage, the description provides essential context about manual execution and root privileges. However, it lacks details about the output (e.g., what the instructions look like) and does not fully compensate for missing parameter descriptions. An output schema exists but its content is unknown.

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 input schema has 0% description coverage, and the description does not explain the parameters 'ownername' and 'projectname'. It only implies they identify the repository, but provides no details on format, source, or validation.

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 clearly states it 'Provide instructions for enabling a Copr repository', specifying the verb 'enable' and resource 'Copr repository'. It is distinct from sibling tools like 'copr_submit_build' or 'copr_create_project', but does not explicitly differentiate itself.

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 mentions that the tool 'requires root privileges and must be run manually by the user', providing usage context about manual execution and permission requirements. However, it does not specify when not to use it or suggest alternative tools.

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