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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds real value beyond that by disclosing the returned field set (id, name, status, scheduled/sent time, automation) and the underlying endpoint, which matters because no output schema exists.

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?

A two-fragment telegraphic description with zero filler, and the resource is front-loaded before the field list. It is terse to the point of being under-written, but nothing is wasted.

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?

For a simple two-param read tool the description is minimally adequate: it identifies the resource and the return fields, partly compensating for the missing output schema. It omits pagination/result-size behavior and any filtering caveats, leaving the schema to carry those.

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% and both parameters (page, limit) are well documented in the schema, including the next_page chaining hint. The description adds nothing about parameters, so the baseline 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?

The description names the resource (email campaigns) and enumerates the fields returned, so an agent can tell it apart from sendlane_get_campaign (singular) and the other list_* siblings like sendlane_list_lists or sendlane_list_tag_contacts. It lacks an explicit verb but the fields plus endpoint make the list semantics unambiguous.

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?

There is no guidance on when to use this versus sendlane_get_campaign (single campaign) or sendlane_get_campaign_report, and no mention of prerequisites, filters, or sorting behavior. The agent must infer usage entirely from the name and schema.

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