deleteWebPage

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

Beyond annotations (destructiveHint, readOnlyHint), description discloses permanence, cascade deletion of associated redirect for data_category, and critical orphan cleanup requirement for `users_meta` rows with detailed workflow and warnings. No contradiction with annotations.

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?

Well-structured with headers, bullet points, and code snippets. Each section adds unique value without redundancy. While detailed, it remains focused and easy to scan.

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?

Covers all aspects: purpose, usage, side effects (redirect cascade, orphan cleanup), warning about incorrect deletion, and return value. No output schema needed as description explains the simple response.

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?

Only one parameter (`seo_id`) with 100% schema coverage. Description adds context by explaining it is the primary key and required, but schema already provides type and description. No further parameter-level details needed beyond what is given.

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?

Description clearly states 'Delete a page - Permanently delete a web page by `seo_id`.' It specifies the action, resource, and required identifier, distinguishing it from sibling tools like `deleteRedirect` and `deleteUserMeta`.

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 explicit when to use ('permanently removing a page'), required parameter (`seo_id`), destructive warning, prerequisites like considering redirects and menu cleanup, cascade behavior for data_category, and step-by-step orphan cleanup instructions with warnings against incorrect deletion. Also references alternative `updateWebPage`.

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