appflowy_delete_page_from_trash

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

Without annotations, the description must disclose behavioral traits. It states 'Permanently delete' implying irreversibility, but lacks details on required permissions, side effects on associated data, or whether it empties from trash permanently.

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 extremely concise at one short phrase. No unnecessary words, but it may be too terse, sacrificing contextual completeness.

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 no annotations, no output schema, and a minimal description, the tool definition lacks crucial context. It does not explain the state of the page before deletion, the impact, or any return value.

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 description coverage is 0%, and the description does not explain the meaning or format of 'workspace_id' and 'page_id'. The description adds no value beyond the schema's property names.

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 'Permanently delete a trashed page' clearly specifies the action (delete), resource (trashed page), and permanence. It directly distinguishes from sibling tools like 'appflowy_move_page_to_trash' and 'appflowy_restore_page_from_trash' by indicating finality.

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 context on when to use this tool versus alternatives. It does not mention prerequisites (e.g., page must be in trash) or exclusions. For a tool with clear siblings, some guidance is expected.

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