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

Annotations already declare destructiveHint=true and readOnlyHint=false, so 'write operation' largely restates structured data. The description does add one piece of novel context — that archiving 'affects project visibility' — but omits reversibility, the confirm-required flow, and non-idempotent retry behavior, all of which matter for a destructive mutation.

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, front-loaded sentences with the operation and its endpoint stated first. Slight waste in 'write operation', which is already covered by annotations, but nothing else bloats the text.

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 destructive, non-idempotent mutation the description covers the basic identity and the visibility side effect, and annotations plus an 86%-covered schema carry the rest. However, it never says whether archiving is recoverable via restore_project, which is the key question an agent needs answered before invoking it.

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 86%, so the required confirm and credential parameters are already documented in the schema. The description only echoes project_id via the endpoint path and adds no format, aliasing, or multi-workspace guidance beyond what the schema states.

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 pair (archives/closes) and the resource (project), and even names the endpoint /projects/close/:project_id. It is clear what the tool does, but it never distinguishes itself from close siblings like delete_project, update_project, or restore_project, so the agent must infer which one applies.

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?

There is no guidance on when to archive rather than delete, update, or duplicate a project, and no mention that restore_project is the inverse. Usage is only implied by the tool name; the description adds no routing information.

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