list_notes

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

Without annotations, the description adds behavioral context by noting the Joplin limit cap on limit and that pages start at 1. It also clarifies notebook_id as a folder id. However, it does not explicitly state read-only status or other 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?

The description is a single clear summary followed by a three-line Args bullet list, with no extraneous content. The information is front-loaded and each line adds value.

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?

With an output schema present, return values are covered externally. The description covers main functionality and parameter constraints, though it could benefit from an explicit read-only note given lack of annotations.

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 Args section explains notebook_id as a folder id filter, limit with Joplin's 100 cap, and page starting at 1, adding semantics beyond the raw schema types. Given 0% schema coverage, this fully compensates for all three parameters.

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 uses a specific verb 'List' with resource 'notes' and clarifies optional notebook filtering. This clearly distinguishes it from siblings like get_note (single note) and search_notes (text search).

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 for listing notes, but does not explicitly discuss alternatives or exclusions. The optional notebook filter provides context, but there is no guidance on when to prefer search_notes or get_note.

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