admin_reactivate_project

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

Discloses mutation behavior, specific field affected, and version change. States authorization requirement (platform-admin). No annotations provided, but description covers key behavioral aspects. Minor omission: no mention of side effects or idempotency, but adequate for scope.

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 sentences, each adding critical information: purpose, behavioral change, and alternatives. No redundancy, front-loaded with key action.

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?

Given single parameter, no output schema, and no annotations, the description fully covers purpose, usage, limitations, and alternatives. Sufficient for an agent to correctly select and invoke the 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 covers 100% of parameter descriptions, but the tool description adds context on what the parameter does in the broader operation and clarifies the limitation about org-level reactivation. Adds 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?

Clearly states the tool un-archives a project by flipping archived_at to NULL. Distinguishes from sibling admin_archive_project and related admin_set_lease_perpetual. Includes endpoint URL.

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 what the tool does and does not do (no org-level lifecycle changes). Gives specific alternative tools for reactivating grace-state orgs: tier_set or admin_set_lease_perpetual. Notes platform-admin only restriction.

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