create_repository

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

Annotations already declare the safety profile (destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description still adds genuine value with the serialization caveat that JSON-encoded string fields must remain strings, a real failure mode for agents. It stops short of stating required permissions, what happens to the request on validation failure, or what is returned.

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 short, front-loaded fragments: verb first, then endpoint, then the encoding constraint. Zero filler, though the telegraphic style leaves some ambiguity about how the 'API fields' passthrough relates to the nested schema.

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 mutating open-world creation tool with two required parameters, a six-property nested object, no field descriptions and no output schema, the description is thin. An agent cannot learn from it which fields are mandatory nor what a successful call returns, so it must reverse-engineer the schema by trial.

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 must carry the load, and it largely does not: it never names the required body fields (name, git_url) nor explains the optional ones (git_branch, ssh_key_id, id). What it does add is the useful framing that body is a passthrough of API fields and the encoding caveat, but no field-level meaning.

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?

"Add repository" gives a specific verb plus resource, reinforced by the concrete endpoint POST /project/{project_id}/repositories. It is clearly distinguishable from siblings such as update_repository, delete_repository and list_repositories, though it never names them explicitly.

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?

There is no statement of when to use creation versus update_repository, no mention of prerequisites (project membership, permissions, whether a project must exist first), and no exclusions. The only guidance is mechanical ('supply API fields in body'), which is not usage selection.

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