pipedrive_notes_list

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing beyond the basic list semantics. It does not state that this is a read-only operation, how pagination behaves (cursor/limit exist in the schema but are unexplained behaviorally), or whether unfiltered listing returns all account notes.

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?

A single front-loaded sentence with no filler, stating the action before the optional scope. It is appropriately sized, though slightly terse for a tool with eight filter parameters.

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 list tool with no output schema and no annotations, the description covers the core purpose but omits pagination behavior, default result size, and the fact that filters are combinable. It is minimally viable rather than complete.

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 documents all eight parameters, which sets the baseline at 3. The description adds only the high-level notion that deal/person/org/lead are valid scoping dimensions, without new syntax, defaults, or interaction semantics.

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?

States a specific verb ('List') and resource ('notes') plus the optional scoping dimensions, so the agent knows exactly what it retrieves. It does not explicitly differentiate itself from sibling read tools like pipedrive_notes_get or pipedrive_note_comments_list, which keeps it from a 5.

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?

Mentions that notes can be scoped to a deal, person, org, or lead, which implies the filter conditions, but there is no explicit when-to-use guidance or contrast with alternatives such as pipedrive_notes_get or pipedrive_note_comments_list. Usage is only inferable.

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