undelete-page

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does disclose the admin/sysop permission requirement, which is valuable. However, it does not mention side effects such as whether history is restored, what happens if the page already exists, or error conditions for non-deleted pages, leaving some behavioral ambiguity.

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 two sentences: the first states the core action, and the second provides a critical permission note. It is front-loaded, efficient, and contains no redundant information.

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 simplicity (4 params, no output schema, no nested objects), the description covers the essential purpose and a key prerequisite. It does not elaborate on return values or edge cases, but for a straightforward restoration action, the provided information is sufficiently complete for an agent to use it correctly in most scenarios.

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?

All parameters (title, user, wiki, reason) are fully described in the schema with 100% coverage. The description adds no additional parameter-level information, so it does not exceed the baseline expected when the schema handles parameter documentation.

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 uses the specific verb 'restore' and identifies the resource as 'a previously deleted wiki page,' clearly distinguishing it from sibling tools like delete-page or create-page. The title 'undelete-page' aligns directly with this purpose, leaving no ambiguity.

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 clearly indicates the intended action (restoring a deleted page) and provides a key prerequisite (admin/sysop rights). While it does not explicitly mention alternatives like create-page or when not to use the tool, the context 'previously deleted' gives clear guidance for the appropriate use case.

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