drip_recent_unsubscribes

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

No annotations are provided, so the description must disclose behavioral traits. It only implies read-only listing but does not mention pagination behavior, rate limits, authentication requirements, or any side effects. The tool has pagination parameters (page, per_page) but no mention of how results are returned.

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 very concise (one sentence) with no wasted words, but it lacks structure such as bullet points or clear separation of purpose from usage. It is acceptable for a simple tool but could be improved by front-loading key details.

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 tool has 6 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain pagination, sorting options, or the format of date bounds. The agent would lack critical information to use the tool correctly.

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%, yet the description only hints at 'date bounds' (likely since and before). It does not explain the format of these parameters, nor does it mention sort, direction, page, or per_page. Four of six parameters are completely undocumented in the description.

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 tool lists recent unsubscribes with optional date bounds. It specifies a verb (list) and resource (unsubscribes), distinguishing it from sibling tools like drip_list_subscribers or drip_unsubscribe_stats.

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?

No guidance on when to use this tool versus alternatives. For example, it does not contrast with drip_unsubscribe (which performs an unsubscribe) or drip_unsubscribe_stats (which may provide aggregate statistics). The description lacks context for appropriate usage.

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