mirrorRepo

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only implies a copy operation without detailing side effects, permissions, or whether existing repositories may be overwritten. There is no mention of needed credentials or rate limits, leaving significant behavioral ambiguity.

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, front-loaded sentence with no wasted words. It immediately communicates the verb and the object, achieving maximum conciseness.

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 tool with 7 parameters, no output schema, and no annotations, a one-sentence description is severely insufficient. It lacks information on prerequisites, return values, side effects, or how this relates to other repository tools. The description cannot adequately prepare an agent to invoke this tool correctly.

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 any of the 7 parameters, and with schema coverage at 71%, there are still unclear parameters like relays and graspServer. While the schema covers most parameters, the description fails to clarify the overall data flow or the role of these parameters in the mirroring process.

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 the action ('Mirror') and the specific resources involved ('GitHub/GitLab repo' and 'gittr.space'), making the core purpose unambiguous. However, it does not explicitly differentiate this from sibling tools like importRemoteToBridge or createRepo, which may overlap in functionality.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as authentication or existing credentials. It does not explicitly exclude any use cases, but it also gives no context for selection.

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