importRemoteToBridge

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

No annotations are present, so the description must carry the full burden. It mentions 'refetch' but does not explain side effects (e.g., overwriting existing repos), authentication requirements, or network behavior. The mutation implications are unclear, making this insufficient for a server-side clone operation.

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 that communicates the core action efficiently. However, the term 'refetch' is vague and the sentence is slightly dense, but no words are wasted.

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 no annotations, no output schema, and four parameters, this minimal description is insufficient. It does not cover return values, error conditions, prerequisites like credentials, or how this interacts with existing bridge repositories, leaving significant gaps for an agent to invoke it 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?

Schema description coverage is 0%, and the description only indirectly adds meaning to cloneUrl ('GitHub/Git URL') and repo ('owner/repo'). It fails to clarify bridgeUrl or ownerPubkey, leaving two of four parameters undefined beyond raw names.

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 ('Server-side git clone into bridge') and the specific resource ('import GitHub/Git URL into owner/repo on gittr'). It distinguishes from sibling tools by focusing on importing external URLs, unlike pushToBridge or mirrorRepo which cover other workflows.

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 usage for importing remote git URLs into a bridge repo, but does not explicitly state when to use this tool over alternatives like pushToBridge or mirrorRepo. No exclusions or alternative names are provided.

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