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

Annotations declare destructiveHint=true and the description justifies it with concrete consequences: everything already in the project becomes public on open, nobody outside can write, email addresses are never hidden-exposed, subprojects and sibling projects stay closed, and the project auto-closes if the repo stops being public. It adds audit (both directions written to the company journal) and timing ('closing takes effect at once') detail that annotations alone do not convey.

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 operation is front-loaded in the first clause, followed by scope, constraints, and authorization in descending priority. The sentences are long and dense with parentheticals, which costs a little readability, but essentially no sentence is filler.

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 destructive, permission-gated mutation with no output schema, the description covers the prerequisites, authorization model, blast radius, side effects, audit trail, and revocability. An agent has everything needed to decide whether to call it and what to warn the user about.

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 coverage is 100%, so projectKey, isPublic, and indexed are already documented in the schema. The description reinforces isPublic semantics and constrains which projectKey values are eligible, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter burden.

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 first sentence states a precise bidirectional operation on a specific resource: open a project to be read by anybody, or close it again. It also delineates the scope of what 'public' covers (board, issues, comments, files, wiki), which separates it from adjacent tools like set_repository_open_source or set_wiki_page_readers.

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?

Explicit preconditions and alternatives are given: only a project with a public repository may be opened, and the description names the concrete ways that state arises (create_project's openSourceRepo, connect_repository with openSource, or the repositories screen). It also names the required authorization (project lead, parent lead, or admin) and an explicit behavioral instruction to confirm with the person before opening.

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