remind_all_pending_invitations

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

Annotations only declare destructiveHint=true; the description adds real behavioral context beyond that: the operation affects every pending invitation, no subsetting exists, and it honestly flags that coverage of batch-created invitations is an unverified inference. It stops short of describing email delivery semantics, failure behavior, or rate limits, which keeps it from a 5.

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 core action and its all-or-nothing scope are front-loaded in the first sentence. The middle paragraph on batch-interface uncertainty and the closing paragraph of frontend URLs are useful for routing but somewhat verbose relative to a one-parameter tool.

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 an output schema present, return values need no explanation, and the description covers scope, irreversibility of scope, and alternatives well. The inference caveat about batch invitations is a nice touch, though delivery/failure details remain undocumented.

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% and the single form_id parameter is fully documented in the schema, so the description adds no syntax or format detail beyond it. Baseline 3 is appropriate when the schema carries the parameter burden.

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 ('Send reminder emails to every pending invitation on a form') and immediately qualifies the scope as all-or-nothing with no subset endpoint. An agent can distinguish this from other invitation-related operations without opening any schema.

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 operation is all-or-nothing and explicitly notes that create/view/delete invitations are not available via this MCP server, routing the agent to the web frontend with concrete URLs. It lacks explicit 'when not to call this' conditions versus siblings, but the scope constraints give clear usage context.

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