admin_set_lease_perpetual

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

With no annotations provided, the description carries full burden. It discloses toggling behavior, effect on grace-state accounts (inline reactivation, returns reactivated: true), auth requirements, and deprecation context. It does not detail error cases or rate limits, but covers key behaviors.

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 that is mostly concise and front-loaded with the main action. Some redundancy with schema (e.g., platform-admin only mentioned in both), but overall efficient for the information conveyed.

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 no output schema and simple parameters, the description covers purpose, behavior, auth, and deprecation. Missing: error conditions, idempotency, or full return format beyond reactivated flag. Still fairly complete for a toggle 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%, providing baseline 3. The description adds significant value by explaining the effects of true/false (pinning all projects, reactivation on grace-state) and deprecation context, going beyond what schema attributes describe.

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 tool toggles a billing account's lease_perpetual escape hatch, with specific verb 'Toggle' and resource 'billing account's lease_perpetual escape hatch'. It also distinguishes from sibling tools by noting it replaces the v1.56 pin_project endpoint, avoiding confusion.

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 provides clear context: platform-admin only, uses allowance wallet for admin auth, and warns about non-admin wallets. It mentions replacement of deprecated endpoint. However, it does not explicitly state when not to use this tool versus alternatives like admin_archive_project or admin_reactivate_project.

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