list_notes

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

Describes a read operation but does not disclose behavioral details such as ordering, pagination, or limits. Since there are no annotations, the description carries the full burden but is adequate for a simple list tool.

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 no extraneous information. Every sentence adds value: action/purpose and prerequisite.

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?

Complete for a simple list tool with a single parameter. The description covers what, why, and prerequisite. No output schema exists, but the return type is implied (list of notes).

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 coverage is 100% for the single parameter `contactId`, and the description adds no additional semantic meaning beyond what the schema provides. Baseline score of 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?

Clearly states the action ('List the saved notes on a contact') and the purpose ('recall context you or the agent captured earlier'). Distinguishes from sibling tools like `create_note` (different action) and `get_contact` (different resource).

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?

Explicitly instructs to use `find_contacts` first to obtain the `contactId`, providing a clear prerequisite and usage pattern.

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