List articles in Apple Notes by folder, returning each article's title, ID, and modification time. Omit the folder to list all articles across all folders.
列出 Apple Notes 中指定文件夹下的所有文章，返回文章标题、ID 和修改时间。不指定文件夹则列出所有文章。
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | 文件夹名称。不指定则列出所有文件夹中的所有文章。 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
没有提供注解，因此描述需要承担说明负担。它披露了返回字段和默认文件夹行为，这很有帮助，但并未说明分页、结果数量限制或结果是否已排序，对于列表工具而言这是一个缺口。
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?
两句话，没有冗余，先说范围，再说默认情况。高效，但可作为泛泛而谈的正确性示例。
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?
对于一个简单的、只有一个可选参数的列表工具来说已经足够完整，它提到了返回字段，因此无需输出架构。只是缺少分页/限制行为。
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?
架构描述覆盖率为 100%，唯一的参数（category）已在架构中完整记录，因此基线为 3。描述只是重复了默认行为，没有为架构添加格式或命名语义。
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?
明确说明了动词+资源（列出文章）以及范围（Apple Notes 中某个文件夹下），并指出了返回字段。它隐含地与 get_article/search_articles 区分开来，但并未明确提及任何同级工具。
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?
通过说明省略文件夹时会列出所有文章，隐含地表达了使用场景，但没有说明何时应优先选择 search_articles 或 get_article，也没有给出任何排除条件。
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.