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

The only behavioral claim, 'write operation', merely restates what readOnlyHint=false already conveys, so it adds no value beyond the annotations. Nothing is said about what the restore does to the project's tasks, whether it is effectively idempotent, who may perform it, or what the response looks like.

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?

Two short sentences, front-loaded with the core action and free of padding. The second sentence is largely redundant with the annotations, which keeps it just short of a 5.

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?

Annotations cover the safety profile (non-read-only, non-destructive, not idempotent) and there is no output schema to explain, so the description is minimally adequate for this mutation tool. It still omits the archived-only precondition, side effects on contained tasks, and any error condition, leaving real gaps for a write operation.

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 83%, so the schema already documents base_url, api_token, account_id, access_token, and app_password. The description only echoes project_id via the endpoint path, adding no new syntax or format meaning. Baseline 3 applies 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?

States a specific verb and resource ('Restores/reopens an archived project') and even names the underlying endpoint path. It implies the precondition (the project must already be archived), which differentiates it from update_project, though it never names or contrasts those siblings 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 word 'archived' hints at the use case, but there is no explicit statement of when to use this tool versus update_project, archive_project, or the other restore_* siblings. No exclusions, prerequisites (auth/owner rights), or workflow context are given.

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