pipedrive_my_overdue_activities

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the filter conditions (past due, not done) but does not mention authorization, side effects, pagination behavior, or response format. This leaves significant gaps for an agent.

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?

Single sentence, front-loaded with the key verb and object. No extraneous words or repetition. Highly efficient.

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 annotations, no output schema, and three undocumented parameters, the description is insufficient to fully understand the tool. It lacks details on output, pagination, error states, and behavior when as_user is omitted. Sibling tools likely have richer descriptions, making this one feel incomplete.

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%; the description adds minimal meaning beyond parameter names. 'as_user' is glossed as 'or as_user', but cursor and limit are not explained. For three parameters, the description fails to clarify their purpose or expected format.

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?

Description clearly states the action (show), resource (overdue activities), and scope (current user or as_user). It effectively distinguishes from siblings like pipedrive_activities_list (all activities) and pipedrive_my_upcoming_activities (upcoming).

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 overdue activities of a user, but does not explicitly state when to use this tool versus alternatives like pipedrive_activities_list or pipedrive_my_upcoming_activities. No guidance on prerequisites or exclusions.

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