workflowy_refresh_nodes_export_cache

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

With no annotations, the description carries full burden. It discloses the tool forces a snapshot and updates a cache, implying a write/mutation operation with potential performance impact. However, it lacks details on permissions, rate limits, or what 'force' entails (e.g., overwriting, triggering background jobs).

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, efficient sentence that front-loads the core action ('Force a fresh snapshot') and purpose ('update the local cache'). Every word adds value without redundancy, making it highly concise and well-structured.

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 0 parameters, no annotations, and an output schema (which handles return values), the description is reasonably complete. It explains what the tool does and its purpose for cache-dependent systems. However, as a mutation tool with no annotations, it could benefit from more behavioral context (e.g., side effects, idempotency).

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 tool has 0 parameters with 100% schema description coverage. The description doesn't need to explain parameters, so it appropriately focuses on behavior. Baseline is 4 for zero-param tools, as no parameter semantics are required.

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 ('Force a fresh /nodes-export snapshot and update the local cache') and specifies the resource (cache used by NEXUS and UUID Navigator). It distinguishes from siblings like 'workflowy_export_node' by focusing on cache refresh rather than data export, though it doesn't explicitly name alternatives.

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 usage when a fresh snapshot is needed for cache-dependent tools (NEXUS/UUID Navigator), but doesn't specify when to use this vs. other cache-related or export tools. No explicit when-not or alternative guidance is provided, leaving context somewhat open.

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