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

Beyond the destructiveHint=true annotation, the description adds real behavioral context: tests stop running and past runs remain in history. That tells the agent the mutation is scoped and partly non-destructive. It stops short of saying whether the project can be restored or what permissions are required, which matters for an irreversible-looking operation.

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 compact sentence, front-loaded with the action and followed immediately by the two consequences that matter. No filler, no repetition of the schema.

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 one-parameter mutation with no output schema, the description covers the essential effects an agent needs before calling it. The remaining gap is reversibility/restore semantics, which is a meaningful omission for a destructiveHint=true tool but not fatal.

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 a single required parameter (projectId) with 100% schema description coverage including the p_… format hint, so the schema already does the work. The description adds no further meaning about the identifier or its scope, making the baseline 3 appropriate.

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?

The description states a specific verb (archive) and resource (project), and critically resolves the tension with the tool name delete_project by clarifying that this is an archival operation, not a hard delete. It also distinguishes the effect from what an agent might assume from the name, so the behavior is unambiguous.

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?

Usage is only implied: an agent can infer this is the tool for retiring a project without deleting its history. There is no explicit when-to-use/when-not, no mention of alternatives such as update_project, and no statement about whether the archive can be reversed or undone.

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