list_folders

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

With no annotations, the description carries the behavioral burden. It discloses the default exclusion of Recently Deleted (a behavioral trait) and mentions the inclusion of note counts. It does not describe format or ordering, but for a simple read-only list tool, this is sufficient. The description adds value beyond the schema.

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, front-loaded with the core function, and no filler. Every phrase earns its place: the first states what it does, the second clarifies a default behavior.

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 optional parameter and no output schema, the description is complete enough: it specifies the resource, the inclusion of counts, and the default exclusion. It does not mention ordering or edge cases, but these are not critical for a listing tool.

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 100%, so baseline is 3. The description adds meaning by stating the default exclude behavior, which clarifies the include_deleted parameter's default (false). This provides useful context beyond the schema's simple 'Include Recently Deleted'.

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 all Notes folders with note counts' uses a specific verb (List), identifies the resource (Notes folders), and adds output detail (note counts), clearly distinguishing it from sibling list_notes. The additional 'Recently Deleted is excluded by default' scopes the operation unambiguously.

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?

Usage is implied: when you need a list of folders with counts, use this tool. However, there is no explicit when-not-to-use guidance or mention of alternatives like list_notes. The context suggests it but does not state it.

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