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

Annotations already mark this as write-oriented and destructive, and the description adds meaningful behavior: private-repo support, automatic republishing on push, the two-step authorization flow, and the no-builds policy. This goes well beyond the structured data without contradicting it.

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?

Four dense, front-loaded sentences with no filler. The main action leads, followed by important caveats: private repos, the authorization handshake, and no-build publishing. Every sentence earns its place.

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 this complexity, the description covers the important caveats: private repos, auth, repeated invocations, and folder behavior. The main gap is that it does not describe what the second call returns, but the schema plus annotations make the invocation otherwise complete.

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 100% parameter coverage, so the baseline is 3. The description does add a little useful context around the folder parameter ('found automatically, or given') and the no-builds behavior, but it does not meaningfully clarify site, repo, or branch beyond the schema.

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 a specific action and resource: publish a site from a GitHub repository and republish on every push. This clearly distinguishes connect_repo from siblings like disconnect_repo or start_upload. The additional constraint 'No builds are run' further sharpens what this tool does.

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 a concrete usage flow: the first call returns an authorization link, and after the person authorizes, the tool must be called again. This tells the agent exactly when and how to use the tool. It does not explicitly name alternatives or exclusion conditions, but the guidance is strong.

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