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

Annotations already cover safety (readOnly=false, destructive=false, idempotent=true), so the bar is lower, and the description still adds real behavioral value: it discloses the two concrete side effects (reappearance in the project list and resumption of scheduled query checks). It stops short of stating auth requirements or error behavior, hence not a 5.

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?

A single sentence that front-loads the action and then the consequences; no filler or redundant restatement of the title.

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?

An output schema exists, so return values needn't be explained, and annotations plus the description together cover the mutation's safety profile and effects. The remaining gap is the undocumented parameters, which is the one thing missing for confident invocation.

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?

Both parameters (organizationId, projectId) have 0% schema description coverage, so the description must compensate, yet it never mentions either parameter or their expected formats. The schema alone leaves the agent guessing at identifier conventions.

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 ('bring back' / restore) and resource (an archived project), and the effect is unambiguous. An agent can distinguish it from archive_project and restore_organization without opening any schema.

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 is implied ('archived project'), which is decent context, but there is no explicit when-to-use guidance or mention of the sibling restore_organization to disambiguate scope. Usage is inferred rather than stated.

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