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

With annotations covering the safety profile (destructiveHint=true, idempotentHint=false), the description adds substantial non-structured context: what state is preserved (completed/cancelled status and closeout), the side effect of the follow-up update_project (resets closeout to DRAFT), the exact error code NOT_ARCHIVED, and the required authorization (Owner/Manager role or org.compliance.manage).

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 dense sentences, front-loaded with the primary effect before the state-preservation caveat, the error case, and the auth requirement. Every clause carries information, though the middle sentence is packed and could be split for readability.

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?

No output schema exists, so the description carries the burden and does so: it covers the effect, preserved state, the distinct follow-up step, the failure mode, and the permission requirement. Nothing an agent needs to invoke this 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?

There is one parameter (projectId) with 0% schema description coverage, so the description must compensate. It refers to 'the project' but never states the expected identifier form (ID vs name) or where to obtain it; for a single self-evident ID parameter this is a minor gap, not a severe one.

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 (unarchive) plus resource (project) with an explicit statement of the effect ('can be changed again and shows in project lists'). It is unambiguously distinct from the archive_project sibling and from update_project, which is named as the separate reopening step.

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 clearly separates this operation from the subsequent status change (update_project) that actually reopens the project, and states the precondition that the project must currently be archived (NOT_ARCHIVED refusal). It gives strong context, though it never explicitly contrasts with archive_project or says when an agent should prefer this over deleting/recreating.

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