github_prepare_repository

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

With no annotations, the description carries the full behavioral burden. It does disclose two important traits: the tool does not submit/create, and authentication must be established out of band. However, it says nothing about whether it navigates to the form, what happens if a form is already partially filled, how it fails when not logged in, or what state it leaves behind — significant gaps for a mutating browser-automation tool.

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?

Two tight sentences with the core behavior and the key constraint front-loaded; no filler. It is arguably too terse, but nothing present is 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?

For a four-parameter tool with no annotations, no output schema, and no parameter documentation, the description covers only the headline behavior and the login prerequisite. It leaves the agent without guidance on parameter meaning or post-call state, which is a meaningful shortfall given how little structured context exists.

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% across four parameters, so the description must compensate and does not: owner, name, visibility, and description are never mentioned. An agent must infer that these map to the form fields from the schema alone, and the enum on visibility is the only self-documenting element.

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?

States a specific verb and resource ('Fill new GitHub repo form') and adds the crucial scope qualifier 'without creating anything,' which separates it from the sibling github_create_repository. It never names that sibling, so differentiation is implied rather than explicit.

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 prerequisite 'Must be logged in manually beforehand' gives real context about when this tool will work, but there is no statement of when to use this versus github_create_repository or what to do after the form is filled. Usage is implied rather than directed.

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