pipedrive_notes_list

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

No annotations are provided, so the description must carry the full behavioral burden. It only states the basic operation and scoping, failing to disclose pagination, sorting, rate limits, or read-only nature. Essential behavioral traits are missing.

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 very short (one sentence) and front-loaded with purpose. However, given 8 parameters and no schema descriptions, it is under-specified; conciseness is not sufficient when substantive details are missing.

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?

With 8 parameters, no output schema, and no annotations, the description is incomplete. It omits pagination (cursor, limit), sorting, user filtering, and return format. Significant gaps exist for a list tool.

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?

The description adds meaning for deal_id, person_id, org_id, and lead_id by mentioning scoping, but it ignores user_id, cursor, limit, and sort. With 0% schema description coverage, the description should compensate more; it partially does for scope params but leaves major parameters undocumented.

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 'List notes' as the verb-resource action, and mentions optional scoping to deal, person, org, or lead, which distinguishes it from other list tools (e.g., pipedrive_activities_list). However, it does not explicitly differentiate from pipedrive_notes_get or other note tools.

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 optional filtering by entities, but does not specify when not to use it (e.g., for a single note use get) or provide alternatives. No exclusions or context for other parameters like user or pagination.

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