create_repository

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

Annotations declare destructiveHint=true, which already covers the safety profile, and readOnlyHint=false. The description adds value beyond annotations by disclosing that description content is sent via stdin and not audited, and that visibility defaults to private. However, it doesn't describe the return value, implications of initializeWithReadme, or any rate-limit behavior, though with destructiveHint set the safety bar is lower.

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?

Three sentences, zero filler. Each sentence earns its place: the first states the primary action and constraint, the second explains visibility defaults, the third discloses the stdin/audit behavior. Front-loaded with the core purpose.

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 create operation with 8 parameters and no output schema, the description covers the most critical behavioral aspects: owner allowlist, visibility defaults, and the stdin audit disclosure. It doesn't explain the substantive difference between 'account' and 'owner' parameters, which are both required and similar in pattern, leaving potential ambiguity. However, the description is reasonably complete given destructiveHint annotations present.

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%, so the description carries the burden of explaining parameters. It explains the visibility semantics (default private, public/internal need explicit request) which adds meaning beyond the enum values. It also clarifies the description parameter is sent via stdin. However, it doesn't elaborate on the remaining parameters (account vs owner distinction, hasIssues, initializeWithReadme, hostname), though 'account' vs 'owner' being separate required fields is notable.

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 tool creates a repository for an explicitly allowed owner, with a specific verb (create) and resource (repository). It distinguishes itself from read tools like get_repository, list_repositories, and mutation tools like update_repository_description by being the creation action.

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 notes 'explicitly allowed owner' as a prerequisite, implying that only certain owners are permitted. It also explains visibility behavior (defaults to private, public/internal must be requested). However, it doesn't reference sibling tools or explicitly state when-not-to-use it, though the context is clear for a create operation.

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