admin_set_lease_perpetual

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

With no annotations, the description carries full burden. It discloses that enabling pins all projects, can reactivate a grace-state organization, uses allowance wallet for auth, and replaces a deprecated endpoint. It does not mention error conditions or rate limits, but the key behavioral effects are covered.

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?

The description is a single paragraph of 5-6 sentences, front-loaded with the main action. Every sentence adds value: purpose, effect, admin-only, replacement. It is dense but not verbose, though minor restructuring could improve readability.

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?

The description effectively covers the tool's behavior, auth, and relation to deprecated endpoint. It lacks output schema info and error handling, but given the simplicity of the tool (toggle boolean, no output schema required), it is sufficiently complete.

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% and both parameters have descriptions. The tool description adds context: it explains the behavior of 'true' and 'false' for lease_perpetual, including inline reactivation, and repeats org_id admin-only note. This adds value beyond the schema, earning above baseline 3.

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 the verb 'toggle', the resource 'organization's lease_perpetual escape hatch', and the effect on project lifecycle. It distinguishes itself from the removed v1.56 pin_project endpoint and sibling tools like admin_archive_project by specifying this is about lease perpetual pinning.

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 description explicitly states when to use (toggle escape hatch) and who can use (platform-admin only). It compares to the replaced v1.56 endpoint. However, it does not explicitly contrast with sibling admin tools like admin_archive_project or admin_reactivate_project, so it lacks clear when-not-to-use guidance.

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