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

Annotations already declare readOnlyHint/idempotent/openWorld=false, and the description usefully clarifies that the tool only returns path+content and the caller performs the write, which resolves any 'write out' ambiguity. 'Uses no AI and no credits' is a real cost trait not present in annotations, but no other behavioral detail (sizing, limits) is added.

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 output format and no filler. The return-value detail is arguably redundant given the output schema, but it is brief.

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 single-parameter, read-only export with an output schema, the description covers format, return shape, and cost. Nothing an agent needs in order to call it correctly is missing.

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% and the single project_id parameter is fully documented there; the description adds no meaning beyond what the schema already provides, so the 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?

Specific verb ('write the project out') plus resource ('as OpenSpec files') and even the exact output layout (one spec.md per subsystem plus system-level). The OpenSpec format name implicitly separates it from projects_export_speckit, though no sibling is named 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?

The phrase 'write them into the repository to put the current spec back' implies the use case (persisting a snapshot of the current spec), but there is no explicit when-to-use/when-not guidance and no pointer to projects_export_speckit or projects_import_openspec as alternatives.

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