create_repository

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

With no annotations, the description carries the full burden. It discloses that the operation occurs on the authenticated account, returns the name/URL/private status, and defaults to public if privacy is not specified. This covers key behavioral traits, though it lacks explicit error or idempotency details.

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 three sentences and every sentence earns its place: purpose, usage trigger, return values, and default behavior. It is front-loaded with the core action and free of fluff.

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 creation tool with 4 parameters, no output schema, and no annotations, the description provides essential context: action, usage, return values, and default privacy. Minor gaps such as not mentioning potential naming conflicts or authentication prerequisites are acceptable given the brief description.

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 100%, so the schema already documents each parameter thoroughly. The description adds marginal value by reinforcing the default privacy behavior, but it does not introduce meaning beyond what the schema already provides, so the baseline of 3 applies.

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 it creates a new repository in the authenticated GitHub account, using a specific verb and resource. It distinguishes from siblings like create_issue and create_pull_request, which target different resource types, and also notes return values.

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?

It explicitly says 'Usa este tool cuando el usuario pida crear, inicializar o agregar un repositorio nuevo', providing clear when-to-use guidance. It does not mention when-not-to-use or explicitly name alternative tools, but the when-to-use is strong enough to guide selection among siblings.

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