notes_list

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It doesn't disclose whether this is a read-only operation, what permissions are required, whether results are paginated, rate limits, or what the output format looks like. The mention of 'optional filtering' hints at some behavior but lacks specifics.

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 extremely concise at 6 words, which is efficient for a simple concept. However, this conciseness comes at the cost of completeness - it's arguably under-specified rather than optimally concise. The single sentence is front-loaded but lacks necessary detail.

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 tool with 5 undocumented parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, how parameters work, or behavioral characteristics. While it states the basic purpose, it leaves too many unknowns for effective agent use given the complexity implied by the parameter count.

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?

With 0% schema description coverage for all 5 parameters, the description provides no information about what parameters exist or their meanings. 'Optional filtering' vaguely references parameters but doesn't name or explain any of them (after, archived, associations, limit, properties). The description fails to compensate for the complete lack of schema documentation.

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 with optional filtering' clearly states the verb ('List') and resource ('notes'), but it's vague about scope and doesn't differentiate from sibling tools like notes_search. It doesn't specify what 'all notes' means (e.g., all accessible notes, all notes in a workspace) or how filtering works.

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?

No guidance is provided on when to use this tool versus alternatives like notes_search or notes_batch_read. The description mentions 'optional filtering' but doesn't explain what filtering capabilities exist or when this tool is preferred over search tools for similar functionality.

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