delete_doc_page

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It states the core destructive action ('Delete') but does not disclose whether the deletion is permanent, whether it cascades to child elements, or any permission requirements. Without this context, an agent cannot fully anticipate side effects.

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, front-loaded sentence with no redundant wording. It is concise, but it may be slightly too minimal, lacking any additional context that could be added without bloating. The structure is clear and direct.

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 is a destructive mutation with no annotations and no output schema, the one-line description is insufficient for full operational context. It does not explain what happens to the page after deletion, whether the operation is reversible, or how to verify success. Sibling tools like delete_doc and update_doc_page indicate a family where more clarity on scope would be valuable.

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?

The input schema has 100% coverage for its three parameters (team_id, doc_id, page_id), so the schema already documents them clearly. The description adds no additional meaning beyond the schema, but the baseline for high schema coverage is 3, and the description is not misleading about parameters.

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 starts with the verb 'Delete' and clearly identifies the resource as 'a page within a ClickUp Doc'. This is specific enough to distinguish from sibling tools like delete_doc (deletes entire doc) and get_doc_page (retrieves a 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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or context. For example, it does not clarify when one would delete a page versus the entire doc, or whether any special permissions are needed. No alternatives are referenced.

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