pipedrive_my_upcoming_activities

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It reveals that the tool returns upcoming activities filtered by days and user, but omits critical details: whether it returns completed activities, pagination behavior (cursor and limit are not explained), output format, or any side effects. The description is minimal for a tool with no annotations.

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, efficient sentence (15 words) that conveys the core purpose and key variations. It is front-loaded and concise with no redundant words.

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 the lack of output schema and 0% schema coverage, the description should cover more. It explains the primary function and two important parameters (days, as_user), but fails to address pagination through cursor and limit, and does not mention the return format. For a simple listing tool, it is minimally adequate but has gaps.

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 schema has 0% description coverage, so the description must compensate. It adds meaning for 'days' (N days, default 7) and 'as_user' (optional string), but provides no explanation for 'cursor' or 'limit' parameters. The description improves understanding for half the parameters but leaves the pagination-related params 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 the action ('Show upcoming activities'), the resource ('activities'), the time scope ('next N days, default 7'), and the user context ('for the current user or as_user'). This distinguishes it from sibling tools like pipedrive_activities_list (which likely lists all activities without user filtering) and pipedrive_my_overdue_activities (which focuses on overdue items).

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 when to use the tool (for upcoming activities of the current user) but does not explicitly provide when-not-to-use or mention alternative tools. It offers clear context but no exclusions or comparisons to siblings like pipedrive_activities_list or pipedrive_my_overdue_activities.

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