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

readOnlyHint=true already tells the agent this is a safe read, so the description is not the sole carrier of behavior. It adds the underlying REST endpoint (GET /api/v2/activities), but says nothing about pagination, rate limits, or result shape for what is clearly a paginated list endpoint.

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?

Two compact sentences with the core purpose front-loaded and no filler. The REST endpoint clause is mildly redundant for an agent but is short and does ground the operation.

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 100% schema coverage and readOnlyHint, the description is close to sufficient, but for a cursor-paginated list with no output schema it never mentions that results paginate or how to continue. An agent must infer pagination purely from the schema's cursor field.

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 all nine parameters including limit, cursor and updated_since are fully documented in the schema. The description merely re-enumerates the filter names, adding no syntax, defaults, or combination semantics beyond the schema — the baseline of 3 applies.

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 and resource ('List activities') and disambiguates the domain term by parenthesizing '(tasks/events)'. It does not explicitly distinguish itself from siblings like pipedrive_list_deals, but those cover different resources so overlap risk is low.

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?

Says the list is 'optionally filtered by filter/owner/deal/person/org/done/updated_since', which implies when each filter applies, but there is no explicit guidance on when to use this versus search tools or which filters combine. Usage is implied rather than stated.

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