notlai_list_folders

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

No annotations. Description states read-only list operation. No mention of pagination, ordering, or return format. Adequate but minimal for a simple list tool.

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?

Two sentences, no fluff. First sentence states core purpose; second adds relevant context. Efficient and front-loaded.

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 is simple; description adequately covers listing folders and hints at folder ID usage. Lacks details on return structure or pagination, but sufficient for basic use.

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?

No parameters; schema coverage 100%. By baseline (0 params = 4), description adds no parameter info but that's acceptable as none needed.

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?

Clear verb+resource: 'List all your folders.' Distinct from sibling folder tools (create, delete). Additional context about using folder IDs for filtering or moving notes adds purpose clarity.

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?

Implied usage: listing folders. No explicit when-to-use or when-not, nor comparison to alternatives like list_notes or list_tags. Basic guidance only.

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