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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing that the operation uses no AI and consumes no credits, and that it returns both path and content. It could still clarify that the tool itself does not persist anything to the repository (the caller does), which would remove residual ambiguity around 'Write the project out'.

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 verb and the concrete output path, and no filler. The phrase 'Write the project out' is slightly ambiguous against the read-only nature of the tool, costing a bit of precision.

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-value explanation is not required, yet the description still summarizes the return (path and content). Combined with annotations and a single fully documented parameter, the definition is nearly complete; only the tool-vs-caller write responsibility could be stated more explicitly.

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?

There is a single parameter with 100% schema description coverage, so the schema fully documents project_id. The description adds no extra meaning about the identifier or its scope, which is the expected baseline when the schema does the heavy lifting.

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 names a specific action and artifact: it writes the project out as one GitHub Spec Kit feature at a concrete path (specs/<NNN>-current-system/spec.md). It implicitly separates itself from siblings like projects_export_openspec and projects_import_speckit by naming the Spec Kit format and direction of flow.

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 states the intended downstream consumer explicitly ('write it into the repository so /speckit-specify reads it'), which tells the agent exactly when this output is useful. It does not, however, compare against projects_export or projects_export_openspec, so the choice among export variants is left to inference.

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