admin_reactivate_project

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

No annotations provided, so description carries burden. It discloses the database update (archived_at to NULL), version change (v1.57 narrowing), permission requirement (platform-admin), and HTTP endpoint. Lacks details on side effects or reversibility but is adequate for a simple field set.

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?

Three efficient sentences, each adding distinct info: core action, limitation/history, alternatives, and permissions/endpoint. No wasted words; front-loaded with primary purpose.

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?

Covers purpose, limitations, alternatives, permissions, and endpoint. Lacks explicit mention of prerequisites (e.g., project must be archived) and error conditions, but is sufficient for a simple single-parameter tool.

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%, baseline 3. The parameter description repeats main info but adds context about v1.57 and when not to use (grace-state). Provides guidance on alternative tools for invalid cases, adding value beyond schema.

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 clearly states it 'flips `projects.archived_at` back to NULL', a specific un-archive action. It distinguishes from siblings by noting it no longer touches organization-level lifecycle and contrasts with `admin_set_lease_perpetual` and `tier_set`.

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?

Explicitly states 'Platform-admin only' and gives when-not: 'it does NOT reactivate a grace-state organization'. Provides clear alternatives: use `tier_set` or `admin_set_lease_perpetual` for grace-state organizations.

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