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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description adds useful context that results are newest first and that the call does not spend credits, but it does not mention pagination behavior, auth requirements, or response size.

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 front-loaded with the core action and then gives scope, ordering, and read-only/no-credit behavior in a compact set of sentences. There is no filler or repetition that wastes the agent's attention.

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?

It gives enough context to understand what is listed and how it is ordered, and annotations cover the safety profile. However, for a filtered list endpoint with no output schema, it omits response shape, pagination expectations, and any guidance on the available filters.

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 never mentions the required prospect ID or the since, category, page, or per_page filters, so it adds no parameter-level meaning. With schema description coverage reported at 0%, the description does not compensate for that gap.

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 states a specific verb and resource: 'List prospect activity' for a prospect's record in this workspace. It also scopes the result set to everything that happened to that prospect, newest first, and enumerates the event categories, which distinguishes it from single-activity and search-oriented siblings.

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 does not say when to use this tool versus alternatives such as the activity search or single-activity endpoints. It implies the use case by saying it lists prospect activity, but provides no explicit when-to-use or when-not-to-use guidance.

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