appflowy_reorder_favorite

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

No annotations are provided, so the description carries full burden. It only states the action (reorder), which implies a write operation, but does not disclose permissions, effects on other favorites, error conditions, or 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?

One sentence, concise and front-loaded. Every word serves a purpose. Could be slightly more structured but overall efficient.

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?

Tool has 3 parameters and no output schema. Description only explains purpose and one parameter. Lacks context on prerequisites (e.g., page must already be in favorites), handling of invalid 'prev_view_id', and any constraints. Inadequate for full understanding.

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%. The description explains only 'prev_view_id' usage ('the favorite to place it after (omit to put it first)'), but omits 'workspace_id' and 'page_id'. Barely adds value beyond the schema.

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 'Reorder a page within the favorites list' with a specific verb and resource. It distinguishes from 'favorite_page' and 'reorder_pages' implicitly, but does not explicitly differentiate from siblings.

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 guidance on the 'prev_view_id' parameter ('omit to put it first'), but lacks any context on when to use this tool versus alternatives like 'reorder_pages' or 'move_page'. No when-not-to-use or prerequisites.

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