Remind survey participants

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

Describes side effect (sending emails), required confirmation, underlying method, and authentication. Annotations provide no contradiction; description adds value beyond annotations.

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?

Three concise sentences: purpose, key requirement, and method/auth. No wasted words.

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?

Covers main behavioral aspects and critical parameter. Output schema exists, so return values are handled. Could mention what happens with no eligible participants, but not essential.

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 baseline is 3. Description adds minimal context (e.g., 'eligible participants' maps to token_ids: false), but largely repeats 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 clearly states the action ('Send reminder emails') and the target ('selected or eligible participants'). It distinguishes from sibling tools like invite or mail participants by specifying 'reminder' and 'eligible' participants.

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?

Explicitly requires confirm_send_email=true and clarifies authentication (do not provide session key). However, it does not explicitly contrast with alternatives like limesurvey_invite_participants.

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