appflowy_list_recent

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the basic purpose without revealing ordering, pagination, result limits, or whether it returns only the current user's recent pages. This leaves significant unknowns.

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 of 7 words, perfectly concise and front-loaded. Every word earns its place with no fluff or repetition.

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?

Despite the tool's simplicity, the description lacks completeness. It does not describe the output format or any return fields (and there is no output schema). For a listing tool, the agent needs to know what fields are returned (e.g., page title, last viewed timestamp) to use the results effectively.

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?

With 0% schema description coverage, the description should explain the required workspace_id parameter. It does not; it only mentions 'in a workspace' generically. The parameter's purpose is somewhat obvious, but the description fails to explicitly describe it, missing an opportunity to add value.

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 'List recently viewed pages in a workspace' clearly states the action (list) and the resource (recently viewed pages). This effectively distinguishes it from sibling tools like appflowy_list_favorites or appflowy_list_trash.

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 implies the tool should be used to retrieve recently viewed pages, but it provides no explicit guidance on when to use this tool versus alternatives (e.g., appflowy_search, appflowy_get_workspace_folder). No when-not-to-use or prerequisites are mentioned.

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