list_notes

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

The description claims to 'list all' notes, which is contradicted by the presence of pagination parameters (page, per_page). It does not disclose pagination behavior, archive filtering, or any other operational constraints. With no annotations, the description fails to adequately describe the actual 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?

The description is brief with two sentences, front-loading the purpose. However, the phrase 'list all' introduces ambiguity. Despite this, the structure is efficient and directly addresses the tool's purpose.

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?

Given no output schema, the description partially covers return values but omits mention of pagination and archive filtering, which are critical for correct usage. The description is incomplete for a list tool with multiple parameters.

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?

All parameters have schema descriptions, so baseline is 3. The description adds value by stating the output fields but does not elaborate on parameter usage or relationships. It meets minimum expectations.

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 clearly states the verb 'list' and the resource 'NotePM notes', and specifies what fields are returned (code, name, description). This differentiates it from sibling tools like 'get_page' (single document) or 'search_pages' (search functionality).

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 does not provide any guidance on when to use this tool versus alternatives like 'search_pages' for filtered queries. No explicit 'when not to use' or contextual hints for selecting this tool among siblings.

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