List Client Notes

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

Description adds no behavioral traits beyond annotations (readOnlyHint, destructiveHint). No mention of auth, rate limits, or response format.

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 languages (English and Spanish) repeat the same content, making it slightly redundant. Could be more concise but still short.

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 pagination, annotations cover safety, and output schema exists. The description is adequate; no major gaps.

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 description coverage is 100%, so the schema already describes parameters. The description adds 'optional pagination', which aligns with limit/offset, but no extra meaning beyond schema.

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 verb 'list', resource 'notes for a client', and scope 'all notes with optional pagination'. Distinguishes from sibling tools like create_client_note and delete_client_note.

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 explicit when/when-not or alternatives. Implied usage is clear (list notes for a client), but no guidance on ordering or filtering beyond pagination.

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