bardo_notes_list

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

Adds context beyond readOnlyHint: states 'never full text' and implies the tool returns previews only. Aligns with annotations and provides useful behavioral constraints.

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?

Two concise sentences with front-loaded purpose and no fluff. Every sentence 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?

Describes returned fields (title/summary/snippet/tags/links) and mentions total_notes for pagination. Adequate for a list endpoint without output schema; could mention response is a list.

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 has 0% description coverage; description adds meaning for limit and offset via pagination hint, but session_token remains undocumented. Partial improvement over schema alone.

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 'List your notes — previews only' and lists the specific fields (title/summary/snippet/tags/links), distinguishing it from other note tools like bardo_note_get (full text) and bardo_note_add.

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?

Provides specific pagination guidance: 'Omit limit for everything; pass it to page through a large list, using the returned total_notes to know how much is left.' Does not explicitly contrast with alternatives, but sibling tools imply when full-text retrieval is needed.

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