pipedrive_people_needing_followup

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

The description discloses the core filter (owned by current/as_user, no next activity), but does not mention pagination behavior, ordering, or what happens with zero results. With no annotations, more detail would be beneficial.

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, front-loaded sentence with no redundancy. It is concise, though it could be slightly expanded to cover parameters without losing efficiency.

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?

Given no output schema and no annotations, the description is minimal. It covers the essential filtering logic but lacks details on return fields, edge cases, or error scenarios, making it adequate but not comprehensive.

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%, and only the 'as_user' parameter is mentioned in the description. The 'cursor' and 'limit' parameters are undocumented, leaving semantic gaps despite the tool's simplicity.

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 uses a specific verb ('Find') and resource ('contacts') along with a clear condition ('no next activity scheduled'), distinguishing this tool from sibling list tools like pipedrive_persons_list and pipedrive_my_open_deals.

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 the tool is used for finding contacts needing follow-up, but does not explicitly state when to use it versus alternatives. No exclusions or comparisons are provided, leaving the agent to infer context.

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