list-templates

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

With no annotations, the description carries the full burden and does well: it discloses result ordering, read-only official templates, 200-character truncation, and the required follow-up call to `read-note`. It does not mention pagination, permissions, or full result fields.

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 compact and front-loaded: it starts with the core list behavior, then adds ordering, template identity, read-only status, truncation behavior, and the follow-up tool. Every sentence carries useful information.

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 list tool with one optional parameter and no output schema, the description covers the key behaviors an agent needs: what is listed, ordering, truncation, and how to retrieve full content. It could be more complete by mentioning pagination or the shape of returned template entries, but it is broadly sufficient.

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%, and the `keyword` parameter is already documented in the schema as fuzzy title matching without search qualifiers. The description adds no parameter-specific meaning beyond the schema, so baseline 3 is appropriate.

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 states a specific verb and resource ('List note templates') and clearly distinguishes custom templates from official bundled templates. It also defines templates as notes with `bookId` of `template`, which makes the resource unambiguous.

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?

It gives useful usage context: official templates are read-only, and full template content requires calling `read-note`. However, it does not explicitly explain when to use this instead of sibling tools like `list-notes` or `search-notes`.

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