appflowy_restore_all_from_trash

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

No annotations are present, and the description only states the action. It does not disclose behavioral traits such as whether the operation is reversible, required permissions, or side effects like how pages are restored (e.g., to original location).

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 sentence, which is concise but too brief. It sacrifices completeness for brevity, omitting important details about parameters and usage. Could be expanded without becoming verbose.

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?

For a simple tool with one required parameter and no output schema, the description should still explain what happens when pages are restored and how the workspace_id is used. It lacks this information, making it insufficient for an agent to use confidently.

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 one parameter (workspace_id) with no description (0% coverage). The description does not provide any meaning or context for this parameter beyond the tool's purpose. The agent gets no help understanding what value to provide.

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 clearly states the action ('Restore all trashed pages') and the resource ('in a workspace'). It distinguishes from sibling tools like 'appflowy_restore_page_from_trash' (single page) and 'appflowy_empty_trash' (permanent deletion). However, it could be more specific about what 'restore' entails (e.g., restoring to original location).

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?

No guidance is provided on when to use this tool versus alternatives like 'appflowy_restore_page_from_trash' or 'appflowy_empty_trash'. The description does not mention any conditions or prerequisites.

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