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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safe-read profile is covered. The description adds only the endpoint path and no pagination, rate-limit, or result-shape context beyond what the schema's page/limit params already say.

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 short fragments with zero filler, and the resource scope is front-loaded before the endpoint reference. The extreme terseness borders on under-specification rather than being genuinely tight, 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 5-parameter read tool with no output schema, the description omits what the response contains (contact fields, next_page linkage) and gives no disambiguation against the near-duplicate sibling. The schema carries most of the parameter burden, so this is adequate but with clear 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?

Schema description coverage is 80%, with from/to/page/limit all documented inline in the schema, so the baseline of 3 applies. The description contributes nothing about parameter usage, such as the from/to pair dependency or pagination flow, that isn't already in the schema.

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 a specific resource ('Contacts that unsubscribed from one list') and scopes it to a single list via the listId path, which implicitly distinguishes it from an account-wide unsubscribed listing. However it is a noun fragment with no verb, and it does not explicitly name the very similarly named sibling sendlane_list_unsubscribed_contacts, so an agent could still conflate the two.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives such as sendlane_list_unsubscribed_contacts or sendlane_list_list_contacts. The only context is the raw GET endpoint path, which tells the agent nothing about selection criteria.

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