listNotes

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the basic operation and optional filter, but does not disclose pagination behavior, result ordering, access control, or any potential side effects. This is minimal for a read operation.

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 a single sentence of six words, concise and front-loaded with the core action and subject. Every word carries meaning; there is no filler or redundancy.

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 no output schema, the description is adequate but leaves out what a note is or what the return value contains. The schema covers parameters, but the description could benefit from mentioning the result type (e.g., an array of note objects) or any default behavior.

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 are fully described in the schema (limit, offset, personId), so the description does not need to add parameter details. The description mentions personId but adds no new meaning beyond the schema; the baseline of 3 is appropriate given the high schema coverage.

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 tool lists notes, using a specific verb and resource. It distinguishes itself from sibling tools like createNote, getNote, and updateNote by indicating the list action, and from other list tools (e.g., listTextMessages) by the resource 'notes'.

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 implies usage for listing notes with an optional personId filter, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. There is no naming of when not to use it or comparison with siblings like listTextMessages or listCalls.

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