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

Annotations already establish write/non-destructive/non-open-world, and the description adds genuinely non-obvious behavior: it uses no AI and no credits, and it discloses exactly how content maps (stories and requirements verbatim, clarifications as answered questions, statuses from tasks.md). It does not state permissions or whether an existing project is overwritten.

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, verb-first and front-loaded, with dense but relevant detail about the mapping and the separate folding step. No 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?

With an output schema present, return values need no explanation, and annotations cover the safety profile. The description supplies the format constraint, the transformation behavior, the no-AI/no-credit trait, and the follow-up step, leaving nothing an agent needs to invoke it correctly.

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% and the single url parameter is fully documented in the schema, including accepted forms (URL, owner/repo, /tree/ link). The description only restates the 'public GitHub repository' constraint, adding little beyond the schema, so baseline 3 applies.

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 (Create) and resource (a project) with the precise input format (public GitHub repo using Spec Kit specs/<feature>/spec.md). This clearly separates it from the OpenSpec and plain-import siblings, though it does not name those alternatives 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?

It implies the correct context (import now, fold features into one backlog separately) and names the follow-up step, but never states when to choose this over projects_import or projects_import_openspec, nor does it give prerequisites beyond 'public' repo.

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