admin_set_lease_perpetual

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

With no annotations provided, the description carries the full burden. It discloses that enabling sets lease_perpetual: true, prevents lifecycle advancement beyond active, projects inherit the state, enabling on grace-state organizations reactivates inline and returns reactivated: true, and that it uses the configured allowance wallet. It omits details like idempotency or error responses but covers essential behavioral traits.

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 moderately concise with no fluff. The first sentence clearly states the main action. It efficiently conveys the behavior, auth requirements, versioning, and API endpoint. Could be slightly more structured (e.g., bullet points) but remains effective.

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 the tool's moderate complexity, the description is fairly complete. It explains the core functionality, project inheritance, reactivation behavior, admin authentication, and the replacement of the old endpoint. With no output schema, it mentions the reactivated: true field in responses. It lacks information about potential errors or pagination but covers the necessary context for an agent to use it correctly.

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% with both parameters well-described. The tool description adds conceptual context ('escape hatch', 'pinned state', 'v1.57+') but does not significantly extend beyond the schema descriptions for the parameters themselves. The schema already explains format, admin requirements, and effects.

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's action: 'Toggle an organization's `lease_perpetual` escape hatch'. It specifies the resource (organization), the effect (pinning state, inheritance, reactivation), and distinguishes itself from the deprecated v1.56 pin_project. Among siblings like admin_archive_project and admin_reactivate_project, this tool's unique purpose is well-defined.

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 on when to use the tool: for toggling the lease_perpetual flag on an organization. It specifies that it is platform-admin only using an allowance wallet, and that it replaces the older pin_project endpoint. However, it does not explicitly state when not to use it or list alternatives for similar admin tasks.

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