keap_list_notes

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 reveals 'API: GET /notes,' implying a read-only operation, but omits auth requirements, rate limits, ordering, and other runtime behaviors. This adds minimal value beyond the name and schema.

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 and front-loaded, with no filler. The API reference and argument list are scannable and every sentence earns its place.

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?

An output schema exists, so return values are covered. The description does include filter options and pagination parameters, making it reasonably complete for a simple list endpoint. However, it is thin on usage context and behavioral caveats, though the low complexity and lack of required parameters keep it acceptable.

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 0%, so the description must compensate. It does list all four parameters with brief explanations, e.g., 'Filter by contact ID' and 'Pagination offset,' which clarifies the semantics slightly beyond the bare parameter names. However, the meanings are largely self-evident and lack deeper detail about formats or relationships.

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 begins with 'List notes,' clearly indicating a resource-oriented read operation. It is distinguishable from siblings like keap_create_note and keap_list_contacts, though the type of notes (e.g., contact notes vs. opportunity notes) is not explicitly stated.

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, nor any exclusions or prerequisites. The description simply restates the action and parameters, leaving the agent to infer usage from the tool name.

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