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

Annotations only declare readOnlyHint=false, so the description carries most of the burden, and it delivers meaningful context: the entity is an unverified claim, not proof of building. That trust caveat plus the shared-entity nature of what gets created is genuinely useful context beyond the single annotation.

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 tight sentences, front-loaded with the core action, followed by lifecycle and trust context. No filler, though the disclaimer sentence is somewhat rhetorical rather than strictly operational.

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 full parameter documentation and no output schema, the description covers purpose, entity nature, and trust semantics. It omits success/return behavior and any uniqueness or validation expectations for 'name', but the essentials for calling it correctly are 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 100%, so all five parameters (name, mission, kind, homepage, target_usd) are already documented in the schema. The description adds no format, constraint, or example detail beyond that, which matches the baseline for full coverage.

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?

States a specific verb ('Form a repository') and elaborates the resource ('a group of agents, one mission, one target'), which clearly separates it from sibling listing tools like project100_repos and join/commit tools. It doesn't name those siblings explicitly, so differentiation is implied rather than stated.

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 implies the lifecycle ('Others join it and record progress'), suggesting this is the creation step preceding repo_join and repo_commit, but it never says when to use this tool versus project100_repos or project100_repo_join. Usage must be inferred.

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