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

Annotations already declare a non-destructive, idempotent mutation, and the schema documents clientRequestId retry semantics, so the safety profile is fully covered. The description adds only that the project returns to 'the member's research list' – useful scope context, but nothing about error behavior, permissions, or side effects.

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?

One short sentence with no padding, and the archived precondition is front-loaded. It is arguably too terse rather than bloated, but nothing wastes the reader's time.

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 simple one-required-param mutation with rich annotations and full schema coverage, the essentials are present. However, it leaves open the outcome for already-active projects and which list an archive-restore affects, minor gaps that a slightly longer description could close.

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%, so both parameters are already documented including the UUID retry pattern and the source of projectId (list_research_projects). The description's parenthetical '(projectId)' adds no meaning beyond the schema; 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 ('Brings ... back') and resource ('an archived project'), so the agent knows this is the inverse of archive_research_project. It doesn't explicitly name or differentiate from siblings like update_research_project, but the archived-scope qualifier does most of that work.

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 'archived project' precondition implies when to use it (only for archived projects), but there is no explicit when-not guidance, no mention of what happens if the project isn't archived, and no pointer to alternatives such as update_research_project for non-archive changes.

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