create_repo

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

Discloses that it signs and broadcasts an on-chain transaction (mutation), returns repository URL, and explains owner_id default behavior. Could mention permissions or error handling, but sufficient given no 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?

Concise at 4 sentences, front-loaded with use case, each sentence adds distinct information without redundancy.

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?

Covers purpose, usage, behavioral aspects, and parameter semantics for a simple tool. Could include error scenarios or return format specifics, but overall complete for agent to use.

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?

Adds value by explaining owner_id is optional and defaults to current context, and that description is optional. However, with 0% schema coverage, more details on name constraints or description length would improve it.

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 remote repository without local initialization, specifying the verb 'create' and resource 'remote repository on Gitopia'. It distinguishes from the sibling 'bootstrap_repo' by noting 'without local initialization'.

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?

Explicitly says 'Use this when you need to create a remote repository... without local initialization' and advises 'Prefer bootstrap_repo if you also want to initialize locally, add files, and push an initial commit.' Also references siblings.

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