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

It discloses the non-obvious side effect of minting a short-lived installation token, which is genuinely valuable because the annotations only say readOnlyHint is false without explaining why. It also documents the 409 failure mode and the prerequisite connection state, making the behavior transparent beyond structured annotations.

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 compact and well-organized: purpose first, then output field details, then usage caveats and error handling. Every sentence adds necessary information and none is redundant with the schema or annotations.

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?

The output schema already covers the return structure, so the description wisely focuses on what the schema cannot: side effects, prerequisites, error conditions, and downstream use. Nothing an agent needs to call this tool successfully 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?

There are zero parameters, so the schema leaves no input semantics to document. The description mentions full_name as an output field and points out how to feed it into import_project, which is useful context even though it is not a parameter explanation. The baseline for a no-parameter tool is satisfied.

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 names the exact operation ('List repos') and the resource scope ('the workspace's GitHub connection can see'), and it anchors the purpose to import_project. This distinguishes it from sibling list tools and connects it to downstream use without ambiguity.

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 explicitly frames usage as a precursor to import_project, warns that the call is not a pure read because it can mint a GitHub installation token, and gives a concrete prerequisite: call connect_github() first if a 409 is returned. This fully guides the agent on when and how to use the tool.

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