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

Adds substantial behavior beyond the annotations: the band and subject prefix, that no Cc is carried, that batches of 2–100 are queued one at a time with a batchId returned, the 25-per-24h and 50-Gmail-send caps, and an enumerated list of refusal codes with their detail fields. This is unusually rich disclosure for a mutation tool.

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 purpose is front-loaded, but the middle is a dense run-on with multiple clauses compressed into single sentences and a stray 'One email is sent at once' fragment. Every fact is relevant, but the packaging makes it harder to scan than it needs to be.

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 no output schema, the description still covers what the agent needs on return — status queued plus batchId for batches — and enumerates every documented refusal path with its detail fields. Nothing material for correct invocation is missing.

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 coverage is 100%, so 3 is the baseline, but the description adds real meaning: bandText's default is spelled out and its override chain described, and 'to: me' vs 'to: recipients' gets concrete destination semantics. renderIds sourcing is also implied via lnkdrp_render_email.

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 — sends dry-run copies of rendered emails from the connected Gmail account — and immediately distinguishes itself from a real send by noting 'Nothing is marked sent and the emails stay sendable.' That is enough for an agent to separate it from lnkdrp_send_email or lnkdrp_render_email.

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?

Explains the two modes precisely, including the prerequisite that 'to: recipients' only works when every recipient is on a dry-run list set by an owner or admin, and points to lnkdrp_get_contact_list's dryRun for that check. It does not explicitly name the sibling it replaces (lnkdrp_send_email), so it's clear context without full alternative routing.

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