delete_ui_page

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

Discloses key behaviors: irrevocable deletion, auto-backup before write, and dry-run default showing content to be lost. No annotations provided, so description fully covers behavioral traits relevant for a delete operation.

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?

Two sentences, front-loaded with key action and resource, no redundant words. Every sentence adds essential 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?

Has output schema (not shown) so return values are covered. Description covers purpose, scope, dry-run, and irreversibility. Lacks details about restoration process from backup, but that is acceptable for a delete 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 0%, so description must compensate. It explains scope types and dry_run behavior (shows full content), but does not describe the 'host' parameter. Partially 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 'Delete a UI page' with specific resource (UI page) and scope types ('activity' or 'remote'), distinguishing it from sibling tools like update_ui_page or get_ui_page.

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?

Provides clear guidance on irreversible nature and dry-run default, telling users to preview before deletion. Does not explicitly list alternatives but the dry-run option serves as cautious usage advice.

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